Get threat models for a specific collection
AI agents call get_threat_models_by_collection to retrieve information from Devici MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves threat models associated with a collection. The 'get' verb and query-oriented description demonstrate a read-only operation that retrieves data without creating, modifying, deleting, or executing external operations. Blast radius is minimal—misuse would only expose existing threat model information.
From the tool's definition Tool name 'get_threat_models_by_collection' and description 'Get threat models for a specific collection' indicate a retrieval/query operation with no modification or side effects.
Attacks that exploit this kind of access
Get threat models for a specific collection. It is categorised as a Read tool in the Devici MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Devici MCP Server MCP server in PolicyLayer and add a rule for get_threat_models_by_collection: 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 Devici MCP Server. Nothing to install.
get_threat_models_by_collection 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_threat_models_by_collection 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_threat_models_by_collection. 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_threat_models_by_collection is provided by the Devici MCP Server MCP server (sdelements/devici-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 →