分页执行查询以处理大型结果集 Args: query: SQL查询语句 page: 页码 (从1开始) page_size: 每页记录数 (默认50) Returns: 分页结果的JSON字符串
AI agents invoke mysql_paginate_results to trigger actions in MySQL MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool executes arbitrary SQL queries supplied by the caller. While named as a 'query/paginate' tool, it accepts a raw SQL string which could include DML or DDL statements beyond SELECT. The sibling tool 'mysql_query' suggests these tools run SQL directly. Since arbitrary SQL execution can include destructive statements, but the primary intent is query execution, Execute is the most appropriate category.
From the tool's definition 'SQL查询语句' (SQL query statement) passed as argument; executes arbitrary SQL queries with pagination. Description says '分页执行查询' (paginated execution of queries).
Documented attack patterns abuse exactly the kind of access mysql_paginate_results gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MySQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_paginate_results:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_paginate_results": {
"limits": [
{
"counter": "mysql_paginate_results_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}mysql_paginate_results stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
分页执行查询以处理大型结果集 Args: query: SQL查询语句 page: 页码 (从1开始) page_size: 每页记录数 (默认50) Returns: 分页结果的JSON字符串. It is categorised as a Execute tool in the MySQL MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for mysql_paginate_results: 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.
mysql_paginate_results is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mysql_paginate_results 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 mysql_paginate_results. 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.
mysql_paginate_results is provided by the MySQL MCP Server MCP server (mangooer/mysql-mcp-server-sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MySQL MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 MySQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.