AI agents call resmea_list_committees 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 metadata about available committees for filtering purposes. It performs a read-only query operation that returns data without modifying, executing, or deleting anything. The blast radius of misuse is minimal—an attacker could only enumerate committee names, which are likely public metadata. No financial, destructive, or code execution capabilities are present.
From the tool's definition Tool name 'list_committees' and description 'List RESMEA metrology committee-name filter values' indicate a retrieval operation with no side effects. The verb 'List' is a query operation that returns available filter values.
Attacks that exploit this kind of access
List RESMEA metrology committee-name filter values. 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_list_committees: 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_list_committees 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_list_committees 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_list_committees. 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_list_committees 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 →