Low Risk

mysql_grants_for_entities

Show grants assigned to roles and users.

How to control mysql_grants_for_entities ↓

What mysql_grants_for_entities does on Mysql

AI agents call mysql_grants_for_entities to retrieve information from Mysql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why mysql_grants_for_entities needs a policy

This tool retrieves and displays existing grant information for database users and roles. It performs no modifications, deletions, or code execution. The blast radius is minimal — an agent can only learn about existing permissions, not change them. The server's stated purpose as 'read-only queries' supports this classification.

From the tool's definition Tool name contains 'show' semantic and description states 'Show grants assigned to roles and users' — a pure query/retrieval operation with no mutation or execution of commands.

Documented attack patterns abuse exactly the kind of access mysql_grants_for_entities gives an agent:

How to control mysql_grants_for_entities

PolicyLayer is an MCP gateway — it sits between your AI agents and Mysql, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_grants_for_entities:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql_grants_for_entities": {}
  }
}

mysql_grants_for_entities is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mysql — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about mysql_grants_for_entities

What does the mysql_grants_for_entities tool do? +

Show grants assigned to roles and users. It is categorised as a Read tool in the Mysql MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_grants_for_entities? +

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

What risk level is mysql_grants_for_entities? +

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

Can I rate-limit mysql_grants_for_entities? +

Yes. Add a rate_limit block to the mysql_grants_for_entities 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_grants_for_entities completely? +

Set action: deny in the PolicyLayer policy for mysql_grants_for_entities. 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_grants_for_entities? +

mysql_grants_for_entities is provided by the Mysql MCP server (mukul975/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mysql tool call.

Start from Mysql, 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.

233 Mysql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.