update_museum

Update an existing museum by ID. Only include fields you want to change. Works even if do_not_import is set. Opening hours and admission prices use nested attributes (include id to update, _destroy to delete).

Server Confd mytours/confd-mcp
Category Write
Risk class Medium
Parameters 00 required

What update_museum does on Confd

AI agents use update_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.

Why update_museum needs a policy

The tool modifies existing museum records in a reversible manner (updates can be undone by subsequent updates). It does not delete data irreversibly, execute arbitrary code, move money, or retrieve data without modification. Write operations carry medium severity due to potential for unintended data modification, but less critical than destructive or financial operations.

From the tool's definition Tool name is 'update_museum' and description states 'Update an existing museum by ID' and 'Only include fields you want to change.' This is a classic write operation that modifies existing data reversibly.

Questions about update_museum

What does the update_museum tool do? +

Update an existing museum by ID. Only include fields you want to change. Works even if do_not_import is set. Opening hours and admission prices use nested attributes (include id to update, _destroy to delete). 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.

How do I enforce a policy on update_museum? +

Register the Confd MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_museum? +

update_museum is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_museum? +

Yes. Add a rate_limit block to the update_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.

How do I block update_museum completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_museum? +

update_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.