deed_accept
Accept a Business Deed transfer — buyer signs acceptance with chain of custody. Creates a new deed container with updated transfer history and optionally re-encrypts with a new passphrase for the buyer. Example: deed_accept({ file:
This record as markdown: /tools/io-github-0nork-0nmcp/deed-accept.md
What deed_accept does on 0nmcp
AI agents use deed_accept to create or update resources in 0nmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 0nmcp environment.
Why deed_accept is rated Medium
This tool creates a new deed container and updates transfer history, which are write operations. While it involves business deed transfers that could have financial implications, it appears to be a document management/signing operation rather than directly moving money or committing financial obligations. The severity is high because misuse could fraudulently transfer business ownership documents.
From the tool's definition Accept a Business Deed transfer — buyer signs acceptance with chain of custody. Creates a new deed container with updated transfer history and optionally re-encrypts with a new passphrase for the buyer.
Attacks that exploit this kind of access
The rule that runs deed_accept safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deed_accept, this is the rule to start with:
deed_accept 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.
The button opens the PolicyLayer dashboard: create your workspace, connect 0nmcp, apply this rule, and every deed_accept call is checked against it from then on.
Questions about deed_accept
Accept a Business Deed transfer — buyer signs acceptance with chain of custody. Creates a new deed container with updated transfer history and optionally re-encrypts with a new passphrase for the buyer. Example: deed_accept({ file:. It is categorised as a Write tool in the 0nmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 0n MCP server in PolicyLayer and add a rule for deed_accept: 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 0nmcp. Nothing to install.
deed_accept 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 deed_accept 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 deed_accept. 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.
deed_accept is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue