AI agents invoke sdd_formal_verify to trigger actions in Musubix. 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.
This tool executes formal verification logic using the Z3 theorem prover, an external computational engine. It runs a proof/solver process against provided requirements, making it an Execute-category tool. The blast radius is medium since it processes data through an external solver but does not inherently modify, delete, or move financial assets.
From the tool's definition "Perform formal verification on EARS requirements using Z3 theorem prover"
Attacks that exploit this kind of access
Perform formal verification on EARS requirements using Z3 theorem prover. It is categorised as a Execute tool in the Musubix MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Musubix MCP server in PolicyLayer and add a rule for sdd_formal_verify: 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.
sdd_formal_verify is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sdd_formal_verify 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.
Set action: deny in the PolicyLayer policy for sdd_formal_verify. 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.
sdd_formal_verify 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →