Add a phone number to a contact.
AI agents use create_contact_phone 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 adding a phone number. It is reversible (the phone number can be removed or updated), so it falls under Write rather than Destructive. The blast radius is low—adding a phone number to a contact record in an ATS poses minimal risk of harm even if misused by an AI agent, as it does not delete data, execute code, or cause financial impact.
From the tool's definition Tool name 'create_contact_phone' and description 'Add a phone number to a contact' indicate creation of a new contact phone record, which is a reversible write operation on applicant tracking system data.
Attacks that exploit this kind of access
Add a phone number to a contact. 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 create_contact_phone: 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.
create_contact_phone 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 create_contact_phone 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 create_contact_phone. 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.
create_contact_phone 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 →