Save the current document (Cmd+S) or Save As
AI agents use affinity_save to create or update resources in Affinity MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Affinity MCP Server environment.
The tool writes or overwrites data (document files) reversibly. While save operations are generally safe and expected, they can overwrite existing files and affect document state. This is a Write action (not Destructive, since users can undo via version history or backups in most creative software).
From the tool's definition Tool name 'affinity_save' with description 'Save the current document (Cmd+S) or Save As' directly performs file write operations that modify the state of documents on disk.
Attacks that exploit this kind of access
Save the current document (Cmd+S) or Save As. It is categorised as a Write tool in the Affinity MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Affinity MCP Server MCP server in PolicyLayer and add a rule for affinity_save: 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 Affinity MCP Server. Nothing to install.
affinity_save 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 affinity_save 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 affinity_save. 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.
affinity_save is provided by the Affinity MCP Server MCP server (sekharmalla/affinity-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 →