AI agents use workflow_contact_to_textedit to create or update resources in Mcp Mac — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Mac environment.
While the tool retrieves contact data (a Read operation), its main purpose is to create a formatted document in TextEdit. Document creation is reversible (documents can be deleted or edited), making this a Write rather than Read or Execute action.
From the tool's definition Tool description states 'create formatted TextEdit document' - this is a Write operation that creates new data in TextEdit. The tool also reads contact information ('Get contact information'), but the primary action is creation/modification.
Attacks that exploit this kind of access
Get contact information and create formatted TextEdit document. It is categorised as a Write tool in the Mcp Mac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Mac MCP server in PolicyLayer and add a rule for workflow_contact_to_textedit: 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 Mac. Nothing to install.
workflow_contact_to_textedit 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 workflow_contact_to_textedit 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 workflow_contact_to_textedit. 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.
workflow_contact_to_textedit is provided by the Mcp Mac MCP server (samicokar/mcp-mac). 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 →