AI agents use upload_museum_cover_image 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/modifies museum records by adding or replacing a cover image—a reversible write operation. It lacks the irreversibility of deletion (Destructive), does not execute arbitrary code (Execute), involves no financial transaction (Financial), and produces side effects beyond mere data retrieval (Read).
From the tool's definition The tool uploads (creates/stores) a cover image for a museum, accepting url, base64, or file_path inputs for image formats up to 10MB. This modifies museum data by attaching a new image asset.
Attacks that exploit this kind of access
Upload a cover image for a museum. Displayed as the hero banner background. Provide exactly one of: url, base64, or file_path. Accepts png, jpeg, webp, gif up to 10MB. 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 upload_museum_cover_image: 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.
upload_museum_cover_image 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 upload_museum_cover_image 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 upload_museum_cover_image. 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.
upload_museum_cover_image 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 →