New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

mysql_table_locks

Show current table locks and waiting processes.

SERVERMcp Windows SOURCEmukul975/mcp-windows-automation
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/mukul975-mcp-windows-automation/mysql-table-locks.md

What mysql_table_locks does on Mcp Windows

AI agents call mysql_table_locks to retrieve information from Mcp Windows without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why mysql_table_locks is rated Low

This tool performs information retrieval about database lock states and waiting processes. It has no side effects, does not modify data, does not execute code, and does not delete or move resources. The query nature and read-only semantics place it firmly in the Read category with low severity, as misuse would only expose diagnostic information rather than cause damage or unwanted changes.

From the tool's definition Tool description states 'Show current table locks and waiting processes' — a read-only query operation that retrieves lock status information without modifying or executing operations.

Questions about mysql_table_locks

What does the mysql_table_locks tool do? +

Show current table locks and waiting processes. It is categorised as a Read tool in the Mcp Windows MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_table_locks? +

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

What risk level is mysql_table_locks? +

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

Can I rate-limit mysql_table_locks? +

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

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Windows's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.