report_issue · Knowledgelib MCP: Risk & Policy

WHAT IT DOES

What report_issue does on Knowledgelib

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

WHY IT NEEDS A POLICY

Why report_issue needs a policy

report_issue creates new data (issue reports) in a knowledge base feedback system. This is a Write operation because it generates records that can be reviewed, prioritized, and potentially acted upon, but the action is reversible—reports can be dismissed, closed, or corrected without destructive side effects. It does not delete data, execute arbitrary code, or access sensitive financial systems.

From the tool's definition Tool description states it 'Flag[s] incorrect, outdated, or broken content' and 'Reports are reviewed and used to prioritize content updates.' This describes creating or submitting a report record (a reversible modification to a feedback/issue tracking…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

report_issue Rate-limited

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

FAQ

Questions about report_issue

What does the report_issue tool do? +

Flag incorrect, outdated, or broken content on a knowledge unit. Reports are reviewed and used to prioritize content updates. It is categorised as a Write tool in the Knowledgelib MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on report_issue? +

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

What risk level is report_issue? +

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

Can I rate-limit report_issue? +

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

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

report_issue is provided by the Knowledgelib MCP server (peterbeck111/knowledgelib-io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.