Return ZeroTrue public API metadata and supported formats.
AI agents call zerotrue_get_api_info to retrieve information from ZeroTrue 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 static API documentation/metadata without side effects, state changes, or triggering external operations. It is informational only, fitting the Read category. The risk is minimal since the returned data is public API information with no capability to modify data, execute code, or cause irreversible changes.
From the tool's definition Tool returns API metadata and supported formats with no modification or execution of external operations. Keywords: 'Return', 'metadata', 'supported formats' indicate passive information retrieval.
Attacks that exploit this kind of access
Return ZeroTrue public API metadata and supported formats. It is categorised as a Read tool in the ZeroTrue MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ZeroTrue MCP Server MCP server in PolicyLayer and add a rule for zerotrue_get_api_info: 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 ZeroTrue MCP Server. Nothing to install.
zerotrue_get_api_info 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 zerotrue_get_api_info 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 zerotrue_get_api_info. 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.
zerotrue_get_api_info is provided by the ZeroTrue MCP Server MCP server (zerotruelcc/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 →