# marchward_execute

Run an action through Marchward

Agent View of the PolicyLayer registry record for `marchward_execute`. HTML page: https://policylayer.com/tools/ai-marchward-mcp-server/marchward-execute

## Facts

- Tool: `marchward_execute`
- Server: Mcp Server (`@marchward/mcp-server`) — https://policylayer.com/tools/ai-marchward-mcp-server.md
- Install: `npx -y @marchward/mcp-server`
- Homepage: https://github.com/marchward/marchward
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "marchward_execute",
    "arguments": {}
  }
}
```

## 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 own definition: "Tool name 'marchward_execute' combined with description 'Run an action through Marchward' indicates execution of actions."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "marchward_execute": {
      "limits": [
        {
          "counter": "marchward_execute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp Server (6)

- `marchward_authorize` — Destructive — https://policylayer.com/tools/ai-marchward-mcp-server/marchward-authorize.md
- `marchward_check_coverage` — Read — https://policylayer.com/tools/ai-marchward-mcp-server/marchward-check-coverage.md
- `marchward_get_decisions` — Read — https://policylayer.com/tools/ai-marchward-mcp-server/marchward-get-decisions.md
- `marchward_list_agents` — Read — https://policylayer.com/tools/ai-marchward-mcp-server/marchward-list-agents.md
- `marchward_bind_policy` — Write — https://policylayer.com/tools/ai-marchward-mcp-server/marchward-bind-policy.md
- `marchward_register_agent` — Write — https://policylayer.com/tools/ai-marchward-mcp-server/marchward-register-agent.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=ai-marchward-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ai-marchward-mcp-server