grant_role_to_user
Grant a role to a user (MySQL 8.0+).
This record as markdown: /tools/mukul975-mcp-windows-automation/grant-role-to-user.md
What grant_role_to_user does on Mcp Windows
AI agents use grant_role_to_user to create or update resources in Mcp Windows, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Windows environment.
Why grant_role_to_user is rated Medium
Granting a role to a user modifies database access control permissions. This is a reversible write operation (roles can be revoked), but it carries high severity because it can escalate privileges and expand what a user is authorized to do in the database system.
From the tool's definition Grant a role to a user (MySQL 8.0+)
Attacks that exploit this kind of access
The rule that runs grant_role_to_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For grant_role_to_user, this is the rule to start with:
grant_role_to_user stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Windows, apply this rule, and every grant_role_to_user call is checked against it from then on.
Questions about grant_role_to_user
Grant a role to a user (MySQL 8.0+). It is categorised as a Write tool in the Mcp Windows MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for grant_role_to_user: 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 Mcp Windows. Nothing to install.
grant_role_to_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the grant_role_to_user 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 grant_role_to_user. 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.
grant_role_to_user is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Windows, and thousands of servers like it.
This server
Across the catalogue