AI agents call mee_get_document to retrieve information from GBMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'get_document' indicates a retrieval operation with no side effects. It appears to be part of a standards query and download system. The absence of mutation keywords (create, update, delete) and the read-oriented context of the server (querying metadata, downloading public documents) point to a Read classification.
From the tool's definition Tool name 'mee_get_document' suggests document retrieval. Server description states it is for 'querying standards metadata and downloading public standard documents.' Sibling tools like 'cfsa_get_standard', 'doc88_get_document' follow read-like patterns.
Attacks that exploit this kind of access
mee_get_document. It is categorised as a Read tool in the GBMCP MCP Server, which means it retrieves data without modifying state.
Register the GB MCP server in PolicyLayer and add a rule for mee_get_document: 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 GBMCP. Nothing to install.
mee_get_document 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 mee_get_document 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 mee_get_document. 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.
mee_get_document is provided by the GB MCP server (loydgik/gbmcp). 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 →