mysql_spatial_distance
Find rows within a certain distance from a point (Cartesian distance).
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-spatial-distance.md
What mysql_spatial_distance does on Mysql Mcp
AI agents call mysql_spatial_distance to retrieve information from Mysql Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mysql_spatial_distance is rated Low
This tool performs a spatial query to locate rows matching distance criteria. It retrieves data without creating, modifying, deleting, or executing arbitrary operations. The Cartesian distance calculation is deterministic and returns results based on existing data. No side effects or state changes occur.
From the tool's definition Tool description states 'Find rows within a certain distance from a point' — a query operation that retrieves filtered data based on spatial criteria. The verb 'Find' and the read-only nature of distance calculations indicate no data modification.
Attacks that exploit this kind of access
The rule that runs mysql_spatial_distance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_spatial_distance, this is the rule to start with:
mysql_spatial_distance is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_spatial_distance call is checked against it from then on.
Questions about mysql_spatial_distance
Find rows within a certain distance from a point (Cartesian distance). It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_spatial_distance: 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. Nothing to install.
mysql_spatial_distance 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 mysql_spatial_distance 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_spatial_distance. 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_spatial_distance is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mysql, and thousands of servers like it.
This server
Across the catalogue