contacts_create_contact
AI agents use contacts_create_contact to create or update resources in Pyfastmail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pyfastmail environment.
Creating contacts is a reversible write operation that modifies account data. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). The 'medium' severity reflects that unintended contact creation could clutter an account but is not catastrophic; users can delete contacts afterward.
From the tool's definition Tool name 'contacts_create_contact' indicates creation of contact records. Server description states the MCP provides 'full access to Fastmail accounts for managing email, contacts, calendars, and file storage' with tools to 'enable comprehensive account…
Attacks that exploit this kind of access
contacts_create_contact. It is categorised as a Write tool in the Pyfastmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pyfastmail MCP server in PolicyLayer and add a rule for contacts_create_contact: 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 Pyfastmail. Nothing to install.
contacts_create_contact 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 contacts_create_contact 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 contacts_create_contact. 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.
contacts_create_contact is provided by the Pyfastmail MCP server (pjosols/pyfastmail-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 →