tx_get

Get a value by key within a transaction

Server KevoDB MCP Server kevodb/kevo-mcp
Category Read
Risk class Low
Parameters 00 required

What tx_get does on KevoDB MCP Server

AI agents call tx_get to retrieve information from KevoDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why tx_get needs a policy

This tool retrieves data from the database within a transactional context but performs no modifications, deletions, or external operations. It is a standard read operation with minimal blast radius—misuse cannot corrupt, delete, or modify data.

From the tool's definition Tool name 'tx_get' and description 'Get a value by key within a transaction' indicate a retrieval operation. The verb 'Get' and context of querying a key-value database confirm read-only semantics.

Questions about tx_get

What does the tx_get tool do? +

Get a value by key within a transaction. It is categorised as a Read tool in the KevoDB MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tx_get? +

Register the KevoDB MCP Server MCP server in PolicyLayer and add a rule for tx_get: 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_get? +

tx_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit tx_get? +

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

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

tx_get 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.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.