reportIssue · Semiotic MCP: Risk & Policy

WHAT IT DOES

What reportIssue does on Semiotic

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

WHY IT NEEDS A POLICY

Why reportIssue needs a policy

An AI agent can call reportIssue faster than any human can review — one bad instruction and it creates or modifies resources in Semiotic by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reportIssue Rate-limited

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

FAQ

Questions about reportIssue

What does the reportIssue tool do? +

Generate a GitHub issue URL for Semiotic bug reports or feature requests. Returns a URL the user can open to submit. For rendering bugs, include the component name, props summary, and any diagnoseConfig output in the body. It is categorised as a Write tool in the Semiotic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on reportIssue? +

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

What risk level is reportIssue? +

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

Can I rate-limit reportIssue? +

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

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

reportIssue is provided by the Semiotic MCP server (semiotic). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.