High Risk →

speclock_build_graph

Build/refresh code dependency graph from imports (JS/TS/Python).

Part of the SpecLock - AI Constraint Engine MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

sgroy10/speclock Execute Risk 3/5

AI agents invoke speclock_build_graph to trigger processes or run actions in SpecLock - AI Constraint Engine. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

speclock_build_graph can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

sgroy10-speclock.yaml
tools:
  speclock_build_graph:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full SpecLock - AI Constraint Engine policy for all 44 tools.

Tool Name speclock_build_graph
Category Execute
Risk Level High

View all 44 tools →

Agents calling execute-class tools like speclock_build_graph have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

speclock_build_graph is one of the high-risk operations in SpecLock - AI Constraint Engine. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the speclock_build_graph tool do? +

Build/refresh code dependency graph from imports (JS/TS/Python).. It is categorised as a Execute tool in the SpecLock - AI Constraint Engine MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on speclock_build_graph? +

Add a rule in your Intercept YAML policy under the tools section for speclock_build_graph. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SpecLock - AI Constraint Engine MCP server.

What risk level is speclock_build_graph? +

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

Can I rate-limit speclock_build_graph? +

Yes. Add a rate_limit block to the speclock_build_graph rule in your Intercept 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 speclock_build_graph completely? +

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

speclock_build_graph is provided by the SpecLock - AI Constraint Engine MCP server (sgroy10/speclock). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on SpecLock - AI Constraint Engine

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.