postTransaction · ResilientDB MCP Server MCP: Risk & Policy

WHAT IT DOES

What postTransaction does on ResilientDB MCP Server

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

WHY IT NEEDS A POLICY

Why postTransaction needs a policy

This tool creates a new blockchain transaction committing an asset transfer. While blockchain transactions are generally irreversible, this is a creation/write operation rather than a deletion. However, severity is high because it involves transferring assets on a blockchain (near-financial), uses private keys, and blockchain writes are effectively permanent — misuse could result in unauthorized asset transfers.

From the tool's definition Post a new asset transaction to ResilientDB using GraphQL. Requires PrepareAsset with: operation, amount, signerPublicKey, signerPrivateKey, recipientPublicKey, and asset. Returns CommitTransaction with transaction ID.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

postTransaction Rate-limited

postTransaction 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": {
    "postTransaction": {
      "limits": [
        {
          "counter": "posttransaction_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 ResilientDB MCP Server, so you can run agents against it safely.

FAQ

Questions about postTransaction

What does the postTransaction tool do? +

Post a new asset transaction to ResilientDB using GraphQL (port 8000). Requires PrepareAsset with: operation (String), amount (Int), signerPublicKey (String), signerPrivateKey (String), recipientPublicKey (String), and asset (JSON). Returns CommitTransaction with transaction ID. It is categorised as a Write tool in the ResilientDB 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 postTransaction? +

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

What risk level is postTransaction? +

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

Can I rate-limit postTransaction? +

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

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

postTransaction is provided by the ResilientDB MCP Server MCP server (rahulkanagaraj786/resilientdb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.