Upload an image file and generate AI description for search
AI agents use upload_image to create or update resources in MCP Knowledge Base Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Knowledge Base Server environment.
This tool creates new data (image uploads) in the Supabase database, making it a Write operation. Severity is medium because malicious image uploads could consume storage, introduce inappropriate content, or pollute the knowledge base search index, but the operation is reversible (sibling tool 'delete_document' confirms deletion is possible). Not Destructive because uploads don't irreversibly overwrite existing data.
From the tool's definition Tool name is 'upload_image' and description states 'Upload an image file'; upload is a write operation that creates new data in the knowledge base. The tool modifies the database by adding image documents.
Attacks that exploit this kind of access
Upload an image file and generate AI description for search. It is categorised as a Write tool in the MCP Knowledge Base Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Knowledge Base Server MCP server in PolicyLayer and add a rule for upload_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 MCP Knowledge Base Server. Nothing to install.
upload_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_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_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_image is provided by the MCP Knowledge Base Server MCP server (maxsmosarski/mcp-knowledge-base). 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 →