test_rule · Autoconsent MCP: Risk & Policy

WHAT IT DOES

What test_rule does on Autoconsent MCP

AI agents invoke test_rule to trigger actions in Autoconsent MCP. 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.

WHY IT NEEDS A POLICY

Why test_rule needs a policy

This tool runs an Autoconsent rule against a real web page in a browser, triggering external browser automation operations whose effects depend on the rule and URL provided. It is not merely reading data; it actively executes rule logic against live sites, which could interact with consent management platforms, click elements, or alter browser state.

From the tool's definition 'Tests the given Autoconsent rule on the given URL' — executes a rule against a live URL in a real browser environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_rule Rate-limited

test_rule stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_rule": {
      "limits": [
        {
          "counter": "test_rule_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about test_rule

What does the test_rule tool do? +

Tests the given Autoconsent rule on the given URL. It is categorised as a Execute tool in the Autoconsent MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_rule? +

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

What risk level is test_rule? +

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

Can I rate-limit test_rule? +

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

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

test_rule is provided by the Autoconsent MCP server (noisysocks/autoconsent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.