AI agents call foodmate_search_standards 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.
Search tools query and retrieve metadata about standards without modifying or executing anything. Even though the description is empty, the naming convention and context of peer tools on a standards metadata server strongly indicate this is a standard database search/query tool. Confidence is slightly reduced due to empty description, but the tool name is sufficiently clear.
From the tool's definition Tool name 'foodmate_search_standards' indicates a search operation, which is a read-only query operation. The function of searching standards metadata aligns with retrieval without side effects.
Attacks that exploit this kind of access
foodmate_search_standards. 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 foodmate_search_standards: 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.
foodmate_search_standards 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 foodmate_search_standards 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 foodmate_search_standards. 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.
foodmate_search_standards 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 →