Search for records in a specific table by column value with proper SQL escaping (safer than manual SQL)
AI agents call search_table_records to retrieve information from MCP Document Converter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from a database table based on search criteria. It performs a SELECT-like operation with built-in SQL escaping protections to prevent injection attacks. There is no indication it can modify (Write), delete (Destructive), execute arbitrary code (Execute), or process payments (Financial). The emphasis on SQL escaping as a safety feature further confirms it is a constrained Read operation.
From the tool's definition Tool description states it "Search[es] for records in a specific table by column value" and is presented as a safe read operation with "proper SQL escaping".
Attacks that exploit this kind of access
Search for records in a specific table by column value with proper SQL escaping (safer than manual SQL). It is categorised as a Read tool in the MCP Document Converter MCP Server, which means it retrieves data without modifying state.
Register the MCP Document Converter MCP server in PolicyLayer and add a rule for search_table_records: 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 MCP Document Converter. Nothing to install.
search_table_records 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 search_table_records 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 search_table_records. 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.
search_table_records is provided by the MCP Document Converter MCP server (kittolau/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 →