Get a single trust boundary, including its passes set
AI agents call get_trust_boundary to retrieve information from Mipiti MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a retrieval operation that fetches existing threat model data from the Mipiti platform. It has no side effects, does not create, modify, or delete data, and does not execute code or move money. It clearly falls under the Read category as a data query operation.
From the tool's definition Tool name is 'get_trust_boundary' and description states 'Get a single trust boundary' — retrieves/queries data with 'get' verb and returns information (the trust boundary and its passes set) without modifying or deleting anything.
Attacks that exploit this kind of access
Get a single trust boundary, including its passes set. It is categorised as a Read tool in the Mipiti MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for get_trust_boundary: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mipiti MCP Server. Nothing to install.
get_trust_boundary is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_trust_boundary rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_trust_boundary. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_trust_boundary is provided by the Mipiti MCP Server MCP server (mipiti/mipiti-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →