refine_threat_model
AI agents use refine_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.
Based on the tool name and server context (Mipiti security posture platform for managing threat models), 'refine_threat_model' most likely modifies or updates an existing threat model, placing it in the Write category. Sibling tools like 'add_asset', 'add_component', etc. are all Write operations, suggesting this tool follows the same pattern. However, the empty description significantly lowers confidence.
From the tool's definition Tool name: 'refine_threat_model'; description is empty and uninformative.
Attacks that exploit this kind of access
refine_threat_model. 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.
Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for refine_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.
refine_threat_model is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the refine_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.
Set action: deny in the PolicyLayer policy for refine_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.
refine_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.
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 →