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

run_powershell

Run a PowerShell script from the dev MCP server.

SERVERMapi Agent Memory SOURCEcabo0m/mapi-agent-memory
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mapi-agent-memory/run-powershell.md

What run_powershell does on Mapi Agent Memory

AI agents invoke run_powershell to trigger actions in Mapi Agent Memory. 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 run_powershell is rated High

Running PowerShell scripts permits execution of arbitrary code whose effects depend on the script arguments and content. This is a classic Execute pattern. Severity is critical because PowerShell has broad system access and can perform destructive, financial, or other high-impact operations depending on the script.

From the tool's definition Tool description states "Run a PowerShell script", which directly invokes arbitrary code execution on the system. PowerShell is a command-line shell capable of executing operating system commands, scripts, and administrative operations.

Questions about run_powershell

What does the run_powershell tool do? +

Run a PowerShell script from the dev MCP server. It is categorised as a Execute tool in the Mapi Agent Memory MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_powershell? +

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

What risk level is run_powershell? +

run_powershell is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_powershell? +

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

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

run_powershell is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Mapi Agent Memory, and thousands of servers like it.

// 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 Mapi Agent Memory'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.