sdd_create_requirements · Musubix MCP: Risk & Policy

WHAT IT DOES

What sdd_create_requirements does on Musubix

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

WHY IT NEEDS A POLICY

Why sdd_create_requirements needs a policy

This tool creates new structured requirements documentation in EARS format. It is a write operation because it generates and stores new data artifacts (requirements documents), which can typically be modified or deleted later. Severity is medium because miscreation of requirements documents could lead to downstream workflow delays or confusion, but the impact is containable and reversible.

From the tool's definition Tool name 'sdd_create_requirements' with description 'Create a new EARS-format requirements document' explicitly indicates document creation, a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sdd_create_requirements Rate-limited

sdd_create_requirements stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sdd_create_requirements": {
      "limits": [
        {
          "counter": "sdd_create_requirements_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Musubix, so you can run agents against it safely.

FAQ

Questions about sdd_create_requirements

What does the sdd_create_requirements tool do? +

Create a new EARS-format requirements document. Returns clarifying questions if context is incomplete. It is categorised as a Write tool in the Musubix MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sdd_create_requirements? +

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

What risk level is sdd_create_requirements? +

sdd_create_requirements is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sdd_create_requirements? +

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

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

sdd_create_requirements is provided by the Musubix MCP server (@nahisaho/musubix-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.