session_add_constraint · Z3/SMT MCP Server MCP

WHAT IT DOES

What session_add_constraint does on Z3/SMT MCP Server

AI agents use session_add_constraint to create or update resources in Z3/SMT MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Z3/SMT MCP Server environment.

WHY IT NEEDS A POLICY

Why session_add_constraint needs a policy

Based on the name and context of sibling tools, this tool likely adds a constraint to an existing Z3 solver session, modifying the session state. This is a Write operation as it creates/modifies data (the session's constraint set) in a reversible way (session_pop/session_reset can undo it). The description is empty, so confidence is reduced.

From the tool's definition Tool name 'session_add_constraint' and sibling tools context (session_push, session_pop, session_reset) suggest managing Z3 solver session state by adding constraints.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

session_add_constraint Rate-limited

session_add_constraint 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": {
    "session_add_constraint": {
      "limits": [
        {
          "counter": "session_add_constraint_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 Z3/SMT MCP Server, so you can run agents against it safely.

FAQ

Questions about session_add_constraint

What does the session_add_constraint tool do? +

session_add_constraint. It is categorised as a Write tool in the Z3/SMT MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on session_add_constraint? +

Register the Z3/SMT MCP Server MCP server in PolicyLayer and add a rule for session_add_constraint: 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 Z3/SMT MCP Server. Nothing to install.

What risk level is session_add_constraint? +

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

Can I rate-limit session_add_constraint? +

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

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

session_add_constraint is provided by the Z3/SMT MCP Server MCP server (newjerseystyle/z3smt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.