Save current document / 現在のドキュメントを保存
AI agents use affinity_save_document to create or update resources in MCP Affinity Designer Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Affinity Designer Server environment.
This tool creates or modifies data reversibly by persisting document changes to storage. It is categorized as Write rather than Destructive because saving is a standard, reversible operation—the document can be modified again or restored from backups.
From the tool's definition Tool name 'affinity_save_document' and description 'Save current document' indicate a file persistence operation that modifies the state of an existing document on disk.
Documented attack patterns abuse exactly the kind of access affinity_save_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Affinity Designer Server, and nothing reaches the server without passing your rules. This is the rule we recommend for affinity_save_document:
{
"version": "1",
"default": "deny",
"tools": {
"affinity_save_document": {
"limits": [
{
"counter": "affinity_save_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}affinity_save_document stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Save current document / 現在のドキュメントを保存. It is categorised as a Write tool in the MCP Affinity Designer Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Affinity Designer Server MCP server in PolicyLayer and add a rule for affinity_save_document: 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 Affinity Designer Server. Nothing to install.
affinity_save_document 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_document 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_document. 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_document is provided by the MCP Affinity Designer Server MCP server (szgk/mcp-affinity-designer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Affinity Designer Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 MCP Affinity Designer Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.