Create an issue in an OverlayQA project. Title is required; severity, type, and description default to medium / design-bug / empty.
AI agents use create_issue to create or update resources in OverlayQA MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OverlayQA MCP environment.
This tool creates new issues (data) in OverlayQA projects. While reversible (issues can typically be deleted or modified), it modifies the state of a project by adding new records. This is a Write operation—it creates data without the ability to undo automatically and without destructive side effects.
From the tool's definition Tool description states 'Create an issue in an OverlayQA project', which is explicitly creating and persisting new data in a project management system.
Attacks that exploit this kind of access
Create an issue in an OverlayQA project. Title is required; severity, type, and description default to medium / design-bug / empty. It is categorised as a Write tool in the OverlayQA MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OverlayQA MCP server in PolicyLayer and add a rule for create_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 OverlayQA MCP. Nothing to install.
create_issue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_issue is provided by the OverlayQA MCP server (overlayqa/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →