rename_threat_model · Mipiti MCP Server MCP: Risk & Policy

WHAT IT DOES

What rename_threat_model does on Mipiti MCP Server

AI agents use rename_threat_model 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 rename_threat_model needs a policy

This tool modifies metadata on an existing threat model resource. It is a reversible change (the old name can be changed back), does not delete or destroy data, does not execute arbitrary code or external operations, and does not involve financial transactions. It is clearly a Write operation with low blast radius since renaming a threat model has minimal side effects on system security posture or compliance state.

From the tool's definition Tool name is 'rename_threat_model' with description stating 'Rename a threat model. Metadata change only, does not create new version.' The action modifies an existing resource (the threat model's name/metadata) reversibly without creating a new version or…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_threat_model Rate-limited

rename_threat_model 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": {
    "rename_threat_model": {
      "limits": [
        {
          "counter": "rename_threat_model_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 rename_threat_model

What does the rename_threat_model tool do? +

Rename a threat model. Metadata change only, does not create new version. 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 rename_threat_model? +

Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for rename_threat_model: 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 rename_threat_model? +

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

Can I rate-limit rename_threat_model? +

Yes. Add a rate_limit block to the rename_threat_model 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 rename_threat_model completely? +

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

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