mysql_spatial_within

Find rows where the geometry is within a specified geometry.

SERVERMysql Mcp SOURCEoci:docker.io/writenotenow/mysql-mcp:v1.0.0

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-spatial-within.md

WHAT IT DOES

What mysql_spatial_within does on Mysql Mcp

AI agents call mysql_spatial_within 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.

RISK

Why mysql_spatial_within is rated Low

This tool performs a spatial query to locate rows matching geometric criteria. It retrieves data without creating, modifying, deleting, or executing arbitrary operations. The blast radius is minimal—it only accesses existing data. No side effects or irreversible actions are involved.

From the tool's definition Tool name 'mysql_spatial_within' and description 'Find rows where the geometry is within a specified geometry' indicate a query operation that retrieves/filters data based on spatial geometry criteria.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql_spatial_within 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_within, this is the rule to start with:

mysql_spatial_within Allowed

mysql_spatial_within is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql_spatial_within": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_spatial_within call is checked against it from then on.

FAQ

Questions about mysql_spatial_within

What does the mysql_spatial_within tool do? +

Find rows where the geometry is within a specified geometry. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_spatial_within? +

Register the Mysql MCP server in PolicyLayer and add a rule for mysql_spatial_within: 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.

What risk level is mysql_spatial_within? +

mysql_spatial_within is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mysql_spatial_within? +

Yes. Add a rate_limit block to the mysql_spatial_within 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.

How do I block mysql_spatial_within completely? +

Set action: deny in the PolicyLayer policy for mysql_spatial_within. 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.

What MCP server provides mysql_spatial_within? +

mysql_spatial_within 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.

KEEP EXPLORING

More on Mysql, and thousands of servers like it.

This server

All 223 Mysql tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →