openspec_setup_hooks

THE RISK

High Risk

Why openspec_setup_hooks needs a policy

Installing or uninstalling Git hooks modifies the repository's hook scripts, which are executable scripts that run automatically on Git events. This constitutes triggering external operations and modifying executable code in the repository.

From the tool's definition Install or uninstall OpenSpec Git hooks

Documented attack patterns abuse exactly the kind of access openspec_setup_hooks gives an agent:

POLICY

How to control openspec_setup_hooks

PolicyLayer is an MCP gateway — it sits between your AI agents and OpenSpec MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for openspec_setup_hooks:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "openspec_setup_hooks": {
      "limits": [
        {
          "counter": "openspec_setup_hooks_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

openspec_setup_hooks 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.

Create a free account and register OpenSpec MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More OpenSpec MCP tools

Write openspec_record_revision Record a design revision when fixing bugs or adjusting design that deviates from the origi Write openspec_reply_review Reply to a review comment Write openspec_request_approval Request approval for a change Write openspec_sync_revisions Sync recorded revisions to design.md or proposal.md before archiving Write openspec_add_review Add a review comment to a change or spec Write openspec_approve_change Approve a change Write openspec_archive_change Archive a completed change proposal. Automatically syncs revisions to design.md before arc Write openspec_batch_update_tasks Batch update multiple task statuses in a change

All 40 OpenSpec MCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in OpenSpec MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about openspec_setup_hooks

What does the openspec_setup_hooks tool do? +

Install or uninstall OpenSpec Git hooks. It is categorised as a Execute tool in the OpenSpec MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on openspec_setup_hooks? +

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

What risk level is openspec_setup_hooks? +

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

Can I rate-limit openspec_setup_hooks? +

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

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

openspec_setup_hooks is provided by the OpenSpec MCP server (lumiaqian/openspec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OpenSpec MCP tool call.

Start from OpenSpec MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →