Medium Risk

create_bug_report

Create an automated bug report from an error

How to control create_bug_report ↓

What create_bug_report does on Obsidian Ai Curator

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

Medium Risk

Why create_bug_report needs a policy

This tool creates a new data structure (a bug report) in the Obsidian vault or external issue tracker. While 'create' operations can be Write or Execute depending on side effects, the specific context of generating a bug report from error data is a data creation operation without irreversible consequences—the report can be edited or deleted afterward.

From the tool's definition Tool name 'create_bug_report' and description 'Create an automated bug report from an error' indicate the tool creates a new document/record (a bug report).

Documented attack patterns abuse exactly the kind of access create_bug_report gives an agent:

How to control create_bug_report

PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Ai Curator, and nothing reaches the server without passing your rules. This is the rule we recommend for create_bug_report:

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

create_bug_report 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.

  1. Create a free account and register Obsidian Ai Curator — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_bug_report

What does the create_bug_report tool do? +

Create an automated bug report from an error. It is categorised as a Write tool in the Obsidian Ai Curator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_bug_report? +

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

What risk level is create_bug_report? +

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

Can I rate-limit create_bug_report? +

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

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

create_bug_report is provided by the Obsidian Ai Curator MCP server (nwant/obsidian-ai-curator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Obsidian Ai Curator tool call.

Start from Obsidian Ai Curator, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

27 Obsidian Ai Curator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.