affinity_close_document · Affinity MCP Server MCP

WHAT IT DOES

What affinity_close_document does on Affinity MCP Server

AI agents use affinity_close_document 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.

WHY IT NEEDS A POLICY

Why affinity_close_document needs a policy

Closing a document is a Write operation because it modifies the application state reversibly—the document remains on disk and can be reopened. It is not Destructive because no data is permanently deleted or overwritten. Severity is medium because misuse could cause loss of unsaved work or disruption to a design workflow, but the effect is limited to the current session and can be recovered by reopening the file.

From the tool's definition Tool name 'affinity_close_document' and description 'Close the current document' indicate the tool closes/modifies the state of an open document without permanently deleting it. This is a reversible operation that alters application state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

affinity_close_document Rate-limited

affinity_close_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "affinity_close_document": {
      "limits": [
        {
          "counter": "affinity_close_document_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Affinity MCP Server, so you can run agents against it safely.

FAQ

Questions about affinity_close_document

What does the affinity_close_document tool do? +

Close the current document. 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.

How do I enforce a policy on affinity_close_document? +

Register the Affinity MCP Server MCP server in PolicyLayer and add a rule for affinity_close_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 Affinity MCP Server. Nothing to install.

What risk level is affinity_close_document? +

affinity_close_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit affinity_close_document? +

Yes. Add a rate_limit block to the affinity_close_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.

How do I block affinity_close_document completely? +

Set action: deny in the PolicyLayer policy for affinity_close_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.

What MCP server provides affinity_close_document? +

affinity_close_document 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.