# marchward_bind_policy

Attach a governance policy to an agent. After binding, every authorize and execute call from that agent is evaluated against this policy.

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

## Facts

- Tool: `marchward_bind_policy`
- 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: Write (Medium 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_bind_policy",
    "arguments": {}
  }
}
```

## Why marchward_bind_policy is rated Medium

This tool modifies the governance configuration of an agent by attaching a policy, which is a reversible write operation. However, it carries high severity because it directly affects how all future authorization and execution decisions are evaluated for the targeted agent — an attacker or misconfigured AI could use this to weaken or bypass security controls, effectively escalating privilege or removing safety…

From the tool's own definition: "'Attach a governance policy to an agent' — binds a policy that controls every subsequent authorize and execute call from that agent"

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents use marchward_bind_policy to create or update resources in Mcp Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Server environment.

## 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_bind_policy": {
      "limits": [
        {
          "counter": "marchward_bind_policy_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp Server (6)

- `marchward_authorize` — Destructive — https://policylayer.com/tools/ai-marchward-mcp-server/marchward-authorize.md
- `marchward_execute` — Execute — https://policylayer.com/tools/ai-marchward-mcp-server/marchward-execute.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_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