AI agents call tag_get to retrieve information from Voog without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries and returns tag data without modifying, creating, or deleting any resources. The GET HTTP method confirms no state changes occur. Blast radius is minimal as it only exposes existing tag information.
From the tool's definition Tool name 'tag_get' and description 'Get a single tag by id' with HTTP method `GET /tags/{id}` indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get a single tag by id (GET /tags/{id}). Returns the full. It is categorised as a Read tool in the Voog MCP Server, which means it retrieves data without modifying state.
Register the Voog MCP server in PolicyLayer and add a rule for tag_get: 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 Voog. Nothing to install.
tag_get 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 tag_get 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 tag_get. 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.
tag_get is provided by the Voog MCP server (runnel/voog-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 →