AI agents call resmea_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.
This tool retrieves and queries metadata about metrology standards from the RESMEA source. It performs a read-only lookup operation that returns standard details based on provided identifiers. There are no side effects, data modifications, code execution, deletions, or financial implications. The narrow scope (standards metadata retrieval) and read-only nature justify low severity classification.
From the tool's definition Tool description states 'Get RESMEA metrology-standard detail by code, search id, or detail URL' - the verb 'Get' indicates retrieval operation with no modification capability. No parameters suggest destructive, write, execute, or financial operations.
Attacks that exploit this kind of access
Get RESMEA metrology-standard detail by code, search id, or detail URL. 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 resmea_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.
resmea_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 resmea_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 resmea_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.
resmea_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 →