export_threat_model_archive
AI agents call export_threat_model_archive 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.
The name implies a read/export operation that retrieves a threat model archive. No description is provided to confirm side effects. Based on naming convention alone, this is likely a Read operation. Confidence is lowered due to the empty description. Severity is medium because exporting a threat model archive could expose sensitive security architecture information.
From the tool's definition Tool name 'export_threat_model_archive' suggests exporting/reading data; description is empty and uninformative.
Attacks that exploit this kind of access
export_threat_model_archive. 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 export_threat_model_archive: 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.
export_threat_model_archive 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 export_threat_model_archive 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 export_threat_model_archive. 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.
export_threat_model_archive 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 →