transfer_document_ownership

Transfer a document between your personal knowledge base and a team knowledge base. You can also optionally assign a category in the target scope during transfer.

SERVERFlowDot MCP Server SOURCEflowdot-llc/mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/flowdot-llc-mcp-server/transfer-document-ownership.md

WHAT IT DOES

What transfer_document_ownership does on FlowDot MCP Server

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

RISK

Why transfer_document_ownership is rated Medium

This tool moves a document from one location to another (personal to team or vice versa) and optionally assigns a category. This is a reversible modification of document ownership/location, making it a Write operation. It does not delete data, execute code, or involve financial transactions.

From the tool's definition Transfer a document between your personal knowledge base and a team knowledge base

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transfer_document_ownership safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer_document_ownership, this is the rule to start with:

transfer_document_ownership Rate-limited

transfer_document_ownership 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": {
    "transfer_document_ownership": {
      "limits": [
        {
          "counter": "transfer_document_ownership_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every transfer_document_ownership call is checked against it from then on.

FAQ

Questions about transfer_document_ownership

What does the transfer_document_ownership tool do? +

Transfer a document between your personal knowledge base and a team knowledge base. You can also optionally assign a category in the target scope during transfer. It is categorised as a Write tool in the FlowDot 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 transfer_document_ownership? +

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

What risk level is transfer_document_ownership? +

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

Can I rate-limit transfer_document_ownership? +

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

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

transfer_document_ownership is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FlowDot MCP Server, and thousands of servers like it.

This server

All 207 FlowDot MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →