AI agents use upload_organization_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 modifies organizational metadata by uploading a new cover image asset. The action is reversible (images can be updated or deleted, as evidenced by sibling tools like delete_organization_cover_image), making it Write rather than Destructive.
From the tool's definition Tool description states 'Upload a cover image for an organization' — this creates/modifies image data for an organization record. The server description confirms it 'manage[s]' logos and images through 'create, update, and retrieve' operations.
Attacks that exploit this kind of access
Upload a cover image for an organization. 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_organization_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_organization_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_organization_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_organization_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_organization_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 →