AI agents call get_museum to retrieve information from Confd without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a data retrieval operation only. It queries and returns museum information without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could enumerate museum records but cannot alter or destroy data.
From the tool's definition Tool name is 'get_museum' and description states it retrieves 'a single museum by ID', which is a query/fetch operation with no side effects. The mention of returning a 'merged_into ID' is metadata about the record state, not a modification action.
Attacks that exploit this kind of access
Get a single museum by ID. If the museum was merged into another record, returns the merged_into ID. It is categorised as a Read tool in the Confd MCP Server, which means it retrieves data without modifying state.
Register the Confd MCP server in PolicyLayer and add a rule for get_museum: 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 Confd. Nothing to install.
get_museum 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 get_museum 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 get_museum. 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.
get_museum is provided by the Confd MCP server (mytours/confd-mcp). 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 →