AI agents call samr_get_technical_committee 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 a technical committee from SAMR (State Administration for Market Regulation) by identifier or URL. It performs a simple data lookup operation with no capability to modify, delete, execute code, or commit financial transactions. This is a straightforward Read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name uses 'get' verb and description states 'Get SAMR technical committee detail', indicating a retrieval operation. No side effects, modification, deletion, or execution capabilities are described.
Attacks that exploit this kind of access
Get SAMR technical committee detail by id or orgDetailView 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 samr_get_technical_committee: 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.
samr_get_technical_committee 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 samr_get_technical_committee 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 samr_get_technical_committee. 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.
samr_get_technical_committee 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 →