add_document_collaborator · Helios-9 MCP Server MCP

WHAT IT DOES

What add_document_collaborator does on Helios-9 MCP Server

AI agents use add_document_collaborator to create or update resources in Helios-9 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Helios-9 MCP Server environment.

WHY IT NEEDS A POLICY

Why add_document_collaborator needs a policy

This tool modifies document access control by adding collaborators, which is a reversible Write operation. It doesn't execute arbitrary code, delete data, or move money. Severity is medium because improper use could grant unintended access to sensitive project documents, but the change can be undone by removing the collaborator.

From the tool's definition Tool description states 'Add a collaborator to a document with specific permissions' — a create/modify operation that grants access rights to an existing document.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_document_collaborator Rate-limited

add_document_collaborator 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": {
    "add_document_collaborator": {
      "limits": [
        {
          "counter": "add_document_collaborator_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 Helios-9 MCP Server, so you can run agents against it safely.

FAQ

Questions about add_document_collaborator

What does the add_document_collaborator tool do? +

Add a collaborator to a document with specific permissions. It is categorised as a Write tool in the Helios-9 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 add_document_collaborator? +

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

What risk level is add_document_collaborator? +

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

Can I rate-limit add_document_collaborator? +

Yes. Add a rate_limit block to the add_document_collaborator 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 add_document_collaborator completely? +

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

add_document_collaborator is provided by the Helios-9 MCP Server MCP server (jakedx6/helios9-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.