deed_open
Open and decrypt a Business Deed (.0nv file). Verifies Ed25519 signature and Seal of Truth, then decrypts all layers. Returns credentials, workflows, configs, and deed metadata. Example: deed_open({ file:
This record as markdown: /tools/io-github-0nork-0nmcp/deed-open.md
What deed_open does on 0nmcp
AI agents call deed_open to retrieve information from 0nmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why deed_open is rated Low
This tool reads and decrypts a file, returning sensitive data including credentials, workflows, and configurations. It does not modify or destroy data — it is a read/decrypt operation. However, the severity is high because it exposes credentials and sensitive business configurations; misuse could lead to credential theft or unauthorized access to downstream systems.
From the tool's definition Open and decrypt a Business Deed (.0nv file). Verifies Ed25519 signature and Seal of Truth, then decrypts all layers. Returns credentials, workflows, configs, and deed metadata.
Attacks that exploit this kind of access
The rule that runs deed_open 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_open, this is the rule to start with:
deed_open is read-only, so it stays allowed. 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_open call is checked against it from then on.
Questions about deed_open
Open and decrypt a Business Deed (.0nv file). Verifies Ed25519 signature and Seal of Truth, then decrypts all layers. Returns credentials, workflows, configs, and deed metadata. Example: deed_open({ file:. It is categorised as a Read tool in the 0nmcp MCP Server, which means it retrieves data without modifying state.
Register the 0n MCP server in PolicyLayer and add a rule for deed_open: 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_open is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the deed_open 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_open. 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_open 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