Join our Newsletter — 33% off our NHI Course
Home› Glossary› Identity Beyond IAM› Tools, Resources, and Prompts
Identity Beyond IAM

Tools, Resources, and Prompts

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Identity Beyond IAM

Tools, resources, and prompts are the three parts of an MCP style interface. Tools are actions an AI can invoke, resources are the data it can retrieve, and prompts are reusable instructions that shape the request. Together they define what the model can access and how it behaves.

What Tools Mean in an MCP Interface

Tools are the action layer of an MCP-style interface. They expose bounded operations the model can invoke, rather than raw system access. That makes them the most obviously “active” part of the interface, because they convert a model request into a controlled action with defined parameters, outputs, and constraints.

In practice, tools matter because they define what the model is allowed to do, not just what it can know. A well-designed tool surface reduces ambiguity, limits side effects, and makes the model’s operational authority easier to govern. A poorly designed one can turn a simple integration into an overbroad execution path.

What Resources Mean and Why They Matter

Resources are the retrieval layer. They let the model access data that informs its response or next step, without turning every item of information into an instruction. In an MCP design, that distinction is important: resources are for reading and context, while tools are for acting.

This separation helps preserve least-privilege design. If a model only needs reference data, it should not be given an action-oriented interface as a substitute. That reduces the chance of unintended operations, limits the blast radius of misuse, and keeps the trust boundary between information access and execution much clearer.

What Prompts Do in the Control Model

Prompts are reusable instructions that shape how the model behaves. They are not data and not actions, but they influence interpretation, task framing, and output style. In an MCP-style interface, prompts often sit between the interface definition and the model’s runtime behaviour.

That makes prompts a governance concern as much as a usability feature. A prompt can steer a model toward safe, consistent behaviour, but it can also be used to bias the model into overreaching if the instruction set is too vague, too powerful, or too open to manipulation. The prompt layer therefore needs the same design discipline as the tool and resource layers.

How the Three Parts Work Together

Tools, resources, and prompts are best understood as a three-part contract. Tools define permitted actions, resources define available context, and prompts define behavioural framing. Together they shape both capability and control, which is why MCP-style interfaces are attractive for building structured AI integrations.

That same structure also creates a security boundary that has to be designed deliberately. If any one part is too permissive, the model may gain more practical authority than intended. The strongest MCP implementations keep the three elements tightly scoped and clearly separated so that retrieval, instruction, and execution do not blur into one another.

Risk and Threat Considerations

Tools, resources, and prompts can be abused when their boundaries are weak. The main risk is not the existence of the interface itself, but the chance that a model is given excessive authority, misleading instructions, or unsafe context that causes it to take actions beyond the operator’s intent.

Failure mechanism: A compromised or poorly governed tool, resource, or prompt path can let an attacker inject instructions, overreach permissions, or misuse trusted model behaviour to access data or trigger actions that should have stayed out of scope.

Impact: The result can be unauthorized data exposure, unintended operations, trust boundary failure, or downstream compromise of connected systems and workflows.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP Agentic AI Top 10 and OWASP Non-Human Identity Top 10 address the attack and risk surface, while NIST SP 800-53 Rev 5 sets the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP Agentic AI Top 10ASI02 — Tool MisuseTools are the agent's runtime action surface.
ASI03 — Identity & Privilege AbuseMCP interfaces can expand model authority if access is not scoped tightly.
Recommendation — Constrain tool invocation and validate every tool call against approved intent. Bind each tool and resource to the minimum authority needed for the task.
OWASP Non-Human Identity Top 10NHI-05 — Overprivileged NHIModel-facing interfaces can expose excessive non-human access if over-scoped.
Recommendation — Reduce model-facing access to the smallest set of actions and data required.
NIST SP 800-53 Rev 5AC-6 — Least PrivilegeTool and resource access should be limited to the minimum necessary authority.
IA-5 — Authenticator ManagementMCP-style access often depends on credentials or tokens that must be governed carefully.
Recommendation — Apply least privilege to every tool, resource, and backing service account. Protect and rotate credentials used by tools and backend services.

Practitioner Guidance

Why practitioners should care: The practical question is not whether an MCP interface is useful, but whether each tool, resource, and prompt is narrowly scoped to the business task it supports. Overbroad capability surfaces are harder to audit, harder to test, and easier to misuse.

Common misunderstanding: Teams sometimes treat prompts as harmless metadata and tools as interchangeable integrations. In reality, prompts can meaningfully change model behaviour, and tools can become execution paths if they are not tightly constrained.

Practitioner takeaway: Design the three parts as separate governance objects, then review them together as one runtime trust boundary.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org