configure_bot_filters · ProduckAI MCP Server MCP

WHAT IT DOES

What configure_bot_filters does on ProduckAI MCP Server

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

WHY IT NEEDS A POLICY

Why configure_bot_filters needs a policy

The tool modifies system configuration (bot filter rules) by adding, removing, and toggling filters. While these are reversible operations (Write rather than Destructive), the ability to enable/disable filters could impact what feedback gets processed, potentially affecting product insights if filters are misconfigured.

From the tool's definition Tool description explicitly states "add, remove, enable/disable filters" - these are reversible write operations that modify the configuration state of bot filtering rules.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

configure_bot_filters Rate-limited

configure_bot_filters 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": {
    "configure_bot_filters": {
      "limits": [
        {
          "counter": "configure_bot_filters_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 ProduckAI MCP Server, so you can run agents against it safely.

FAQ

Questions about configure_bot_filters

What does the configure_bot_filters tool do? +

Manage bot filters to prevent bot messages from being processed as feedback. View, add, remove, enable/disable filters. Supports exact name matching, regex patterns, and bot IDs. Default filters included for common bots (Slackbot, GitHub, JIRA, etc.). It is categorised as a Write tool in the ProduckAI 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 configure_bot_filters? +

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

What risk level is configure_bot_filters? +

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

Can I rate-limit configure_bot_filters? +

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

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

configure_bot_filters is provided by the ProduckAI MCP Server MCP server (rohitsaraff33-bit/produckai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.