This record as markdown: /tools/ai-marchward-mcp-server/marchward-execute.md
What marchward_execute does on Mcp Server
AI agents invoke marchward_execute to trigger actions in Mcp Server. 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 marchward_execute is rated High
The tool explicitly 'runs' an action, which is the definition of Execute category. While Marchward provides guardrails (approval gates, spend caps, audit logs), the tool itself triggers external operations whose effects depend on what action is passed as argument.
From the tool's definition Tool name 'marchward_execute' combined with description 'Run an action through Marchward' indicates execution of actions.
Attacks that exploit this kind of access
The rule that runs marchward_execute safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For marchward_execute, this is the rule to start with:
marchward_execute 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 Server, apply this rule, and every marchward_execute call is checked against it from then on.
Questions about marchward_execute
Run an action through Marchward. It is categorised as a Execute tool in the Mcp Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Server MCP server in PolicyLayer and add a rule for marchward_execute: 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 Server. Nothing to install.
marchward_execute 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 marchward_execute 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 marchward_execute. 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.
marchward_execute is provided by the Mcp Server MCP server (@marchward/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
Across the catalogue