Get threats for a specific component
AI agents call get_threats_by_component 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 queries and retrieves threat information associated with a component. It performs a read-only operation that returns existing data without creating, modifying, deleting, executing code, or committing financial actions. The blast radius of misuse is minimal—an agent could retrieve unauthorized threat data, but this is a confidentiality concern rather than an integrity or availability risk.
From the tool's definition Tool name is 'get_threats_by_component' and description states 'Get threats for a specific component'. The 'get' prefix and retrieval-oriented language indicate data querying without modification or side effects.
Attacks that exploit this kind of access
Get threats for a specific component. 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_threats_by_component: 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_threats_by_component 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_threats_by_component 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_threats_by_component. 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_threats_by_component 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 →