Get current threat statistics and audit log
AI agents call get_threat_report to retrieve information from ZugaShield without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches threat statistics and audit logs, which are informational queries with no capability to modify, delete, or execute external operations. The blast radius of misuse is minimal—an agent could only access security telemetry that may already be available through other means. No destructive, financial, or code execution capabilities are present.
From the tool's definition Tool name is 'get_threat_report' and description states it retrieves 'current threat statistics and audit log' — purely read-only operations that query existing data without modification or side effects.
Attacks that exploit this kind of access
Get current threat statistics and audit log. It is categorised as a Read tool in the ZugaShield MCP Server, which means it retrieves data without modifying state.
Register the ZugaShield MCP server in PolicyLayer and add a rule for get_threat_report: 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 ZugaShield. Nothing to install.
get_threat_report 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_report 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_report. 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_report is provided by the ZugaShield MCP server (zuga-technologies/zugashield). 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 →