add_trust_boundary · Mipiti MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_trust_boundary does on Mipiti MCP Server

AI agents use add_trust_boundary to create or update resources in Mipiti MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mipiti MCP Server environment.

WHY IT NEEDS A POLICY

Why add_trust_boundary needs a policy

This tool creates a new trust boundary artifact within a threat model. Trust boundaries are core threat modeling constructs that define security domains. Creating or modifying these is a reversible write operation—new trust boundaries can be edited or removed. The 'add_' prefix and context of programmatic threat model management classify this as Write rather than Execute or Destructive.

From the tool's definition Tool name 'add_trust_boundary' combined with 'add_*' pattern used across all sibling tools that create/modify threat model artifacts (add_asset, add_assumption, add_attacker, add_component, add_evidence, add_functional_test, add_model_to_system,…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_trust_boundary Rate-limited

add_trust_boundary stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_trust_boundary": {
      "limits": [
        {
          "counter": "add_trust_boundary_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mipiti MCP Server, so you can run agents against it safely.

FAQ

Questions about add_trust_boundary

What does the add_trust_boundary tool do? +

add_trust_boundary. It is categorised as a Write tool in the Mipiti MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_trust_boundary? +

Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for add_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.

What risk level is add_trust_boundary? +

add_trust_boundary is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_trust_boundary? +

Yes. Add a rate_limit block to the add_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.

How do I block add_trust_boundary completely? +

Set action: deny in the PolicyLayer policy for add_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.

What MCP server provides add_trust_boundary? +

add_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.