Scan keys in KevoDB with options
AI agents call scan 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.
Scanning keys retrieves data from the database without modifying, deleting, or executing arbitrary operations. It has minimal blast radius—even if an agent scans the entire keyspace, no data is altered or destroyed. This is a standard Read category operation.
From the tool's definition Tool name 'scan' and description 'Scan keys in KevoDB with options' indicate a retrieval operation. The sibling tools list shows typical read operations (get, get_stats) separate from write (put, batch_write) and delete operations, positioning scan as a…
Attacks that exploit this kind of access
Scan keys in KevoDB with options. It is categorised as a Read tool in the KevoDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KevoDB MCP Server MCP server in PolicyLayer and add a rule for scan: 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.
scan 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 scan 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 scan. 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.
scan 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.
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 →