disable_pyfilter · Firegex MCP: Risk & Policy

WHAT IT DOES

What disable_pyfilter does on Firegex

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

WHY IT NEEDS A POLICY

Why disable_pyfilter needs a policy

Disabling a security filter is a reversible state modification (Write category) rather than irreversible deletion (Destructive), though it does weaken security controls. Severity is medium because disabling a firewall filter could allow malicious traffic through, but the impact depends on what the filter protects and the agent's broader access.

From the tool's definition Tool name 'disable_pyfilter' indicates modification of filter state; description states 'Disable a single pyfilter by name' which is a configuration change operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disable_pyfilter Rate-limited

disable_pyfilter 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": {
    "disable_pyfilter": {
      "limits": [
        {
          "counter": "disable_pyfilter_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 Firegex, so you can run agents against it safely.

FAQ

Questions about disable_pyfilter

What does the disable_pyfilter tool do? +

Disable a single pyfilter by name. It is categorised as a Write tool in the Firegex MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on disable_pyfilter? +

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

What risk level is disable_pyfilter? +

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

Can I rate-limit disable_pyfilter? +

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

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

disable_pyfilter is provided by the Firegex MCP server (umbra2728/firegex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.