Fetch records from a table with optional filters, field selection, sorting, and pagination. Returns up to 1000 rows max.
AI agents call fetch to retrieve information from MySQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The fetch tool retrieves data from a database table with filtering and pagination options but does not create, modify, delete, or execute arbitrary code. It is purely a read operation with no side effects. The 1000-row limit further constrains potential blast radius.
From the tool's definition Tool name 'fetch' and description states it 'Fetch records from a table with optional filters, field selection, sorting, and pagination. Returns up to 1000 rows max.' This is a retrieval operation with no modification capability.
Attacks that exploit this kind of access
Fetch records from a table with optional filters, field selection, sorting, and pagination. Returns up to 1000 rows max. It is categorised as a Read tool in the MySQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for fetch: 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 MySQL MCP Server. Nothing to install.
fetch 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 fetch 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 fetch. 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.
fetch is provided by the MySQL MCP Server MCP server (zoherr/mysql-mcp-server). 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 →