Medium Risk

make_rules

Turn a plain-English policy into a jailbreak-proof guardrail. Write rules the way you would explain them to a colleague — ICME compiles them into formal logic (SMT-LIB) that a mathematical solver enforces. No prompt engineering. No LLM judges. The solver either proves an action complies or it doe...

Risk signalsHandles credentials or secrets (api_key)

Part of the Icme Preflight server.

make_rules can modify Icme Preflight data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE ICME PREFLIGHT →

Free to start. No card required.

AI agents use make_rules to create or modify resources in Icme Preflight. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call make_rules repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Icme Preflight.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "make_rules": {
      "limits": [
        {
          "counter": "make_rules_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Icme Preflight policy for all 14 tools.

Get this rule live on your own Icme Preflight server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ICME PREFLIGHT →

View all 14 tools →

These attack patterns abuse exactly the kind of access make_rules gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so make_rules only ever does what you allow.

SECURE ICME PREFLIGHT →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the make_rules tool do? +

Turn a plain-English policy into a jailbreak-proof guardrail. Write rules the way you would explain them to a colleague — ICME compiles them into formal logic (SMT-LIB) that a mathematical solver enforces. No prompt engineering. No LLM judges. The solver either proves an action complies or it doesn't. Returns a policy_id and test scenarios for review. Costs 300 credits. Requires api_key.. It is categorised as a Write tool in the Icme Preflight MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on make_rules? +

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

What risk level is make_rules? +

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

Can I rate-limit make_rules? +

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

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

make_rules is provided by the Icme Preflight MCP server (https://api.icme.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Icme Preflight tool call.

Deterministic rules across all 14 Icme Preflight tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.