AI agents call ttbz_get_standard 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.
Based on sibling tool patterns (cfsa_get_standard, doc88_get_document) and the server's stated purpose of querying and downloading public standards, this tool most likely retrieves standard metadata or documents. No indication of write, delete, execute, or financial operations. The empty description lowers confidence slightly, but the naming convention and server context strongly suggest read-only retrieval.
From the tool's definition Tool name 'ttbz_get_standard' follows the naming pattern of sibling tools like 'cfsa_get_standard' and 'doc88_get_document', which are retrieval operations. Server description emphasizes 'querying standards metadata and downloading public standard documents'.
Attacks that exploit this kind of access
ttbz_get_standard. 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 ttbz_get_standard: 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.
ttbz_get_standard 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 ttbz_get_standard 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 ttbz_get_standard. 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.
ttbz_get_standard 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 →