tx_put · KevoDB MCP Server MCP: Risk & Policy

WHAT IT DOES

What tx_put does on KevoDB MCP Server

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

WHY IT NEEDS A POLICY

Why tx_put needs a policy

This tool modifies data (stores/updates key-value pairs) but operates within a transaction, making changes reversible via rollback_transaction. It does not delete data irreversibly (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or trigger external operations with unpredictable effects.

From the tool's definition Tool name 'tx_put' and description 'Store a key-value pair within a transaction' indicate creation/modification of data within transactional context. The 'put' operation creates or modifies key-value pairs reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tx_put Rate-limited

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

FAQ

Questions about tx_put

What does the tx_put tool do? +

Store a key-value pair within a transaction. It is categorised as a Write tool in the KevoDB 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 tx_put? +

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

What risk level is tx_put? +

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

Can I rate-limit tx_put? +

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

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

tx_put is provided by the KevoDB MCP Server MCP server (kevodb/kevo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.