AI agents use create_issue to create or update resources in Mantis — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mantis environment.
Creating an issue is a reversible write operation that adds structured data to the Mantis bug tracker. While it creates new records, it does not execute code, delete data, or move money, making it a Write-category action. Severity is medium because an AI agent misusing this could spam or pollute the issue database, but the data is retrievable and can be cleaned up.
From the tool's definition Tool name 'create_issue' and description stating it creates ('新增' = 'adds/creates') a Mantis issue. This is a write operation that creates new data in the issue tracking system.
Attacks that exploit this kind of access
新增一個 Mantis 問題. It is categorised as a Write tool in the Mantis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mantis 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 Mantis. 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 Mantis MCP server (mantis-mcp-server). 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 →