AI agents use create_museum to create or update resources in Confd — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Confd environment.
This tool creates new records in the museum database. While creation is reversible (records can be updated or deleted by other tools on this server), the blast radius is medium because an AI agent could spam the database with invalid museum records, pollute the catalog, or create fraudulent entries that require manual cleanup.
From the tool's definition Tool name 'create_museum' and description 'Create a new museum' directly indicates data creation. The parameters (name, contact info, address, social media, tags, opening hours, admission prices) are all reversible additions to a database.
Attacks that exploit this kind of access
Create a new museum. Name is required. Can include contact info, address, social media, tags, opening hours, and admission prices. It is categorised as a Write tool in the Confd MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Confd MCP server in PolicyLayer and add a rule for create_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.
create_museum is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →