admin_run
Run an allowlisted elevated Windows admin action through the scheduled-task broker.
This record as markdown: /tools/mcp-control-plane/admin-run.md
What admin_run does on Mcp Control Plane
AI agents invoke admin_run to trigger actions in Mcp Control Plane. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why admin_run is rated High
This tool executes arbitrary administrative actions on Windows systems with elevated privileges via scheduled-task broker. Although the description mentions 'allowlisted' which provides some constraint, the execution of elevated admin actions can have significant side effects depending on what actions are allowlisted and how an agent uses them.
From the tool's definition Tool description states 'Run an allowlisted elevated Windows admin action through the scheduled-task broker.' The word 'Run' combined with 'elevated' privilege level and 'admin action' indicates execution of administrative commands with elevated permissions.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs admin_run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For admin_run, this is the rule to start with:
admin_run stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every admin_run call is checked against it from then on.
Questions about admin_run
Run an allowlisted elevated Windows admin action through the scheduled-task broker. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for admin_run: 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 Control Plane. Nothing to install.
admin_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the admin_run 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 admin_run. 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.
admin_run is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue