upload_contact_attachment
AI agents use upload_contact_attachment to create or update resources in CATS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CATS MCP Server environment.
This tool creates or modifies contact data by attaching a file, making it a Write operation. Severity is medium because unauthorized file uploads could introduce malicious content, compromise data integrity, or expose sensitive candidate information, but the operation is reversible (attachments can typically be removed).
From the tool's definition Tool name 'upload_contact_attachment' indicates file upload functionality. Sibling tools in the CATS recruiting system show patterns of modifying data (attach_*_tags, authorize_*, change_*_thumbnail).
Attacks that exploit this kind of access
upload_contact_attachment. It is categorised as a Write tool in the CATS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CATS MCP Server MCP server in PolicyLayer and add a rule for upload_contact_attachment: 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 CATS MCP Server. Nothing to install.
upload_contact_attachment 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_contact_attachment 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_contact_attachment. 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_contact_attachment is provided by the CATS MCP Server MCP server (vanman2024/cats-mcp-server). 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 →