AI agents use pleasanter_create_issue to create or update resources in Pleasanter MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pleasanter MCP Server environment.
Creating new issues is a reversible write operation—issues can be updated or deleted afterward. It has moderate severity because bulk issue creation could clutter the project management system, but the action is not irreversible (unlike delete/destructive operations) and does not execute arbitrary code or move money.
From the tool's definition Tool name contains 'create_issue' and description states '新しい課題を作成します' (creates new issues in Pleasanter). This is a create operation that adds data to the system.
Documented attack patterns abuse exactly the kind of access pleasanter_create_issue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pleasanter MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for pleasanter_create_issue:
{
"version": "1",
"default": "deny",
"tools": {
"pleasanter_create_issue": {
"limits": [
{
"counter": "pleasanter_create_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pleasanter_create_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.
Free to start. No card required.
Pleasanterで新しい課題を作成します. It is categorised as a Write tool in the Pleasanter MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pleasanter MCP Server MCP server in PolicyLayer and add a rule for pleasanter_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 Pleasanter MCP Server. Nothing to install.
pleasanter_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 pleasanter_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 pleasanter_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.
pleasanter_create_issue is provided by the Pleasanter MCP Server MCP server (takashi-matsumura/pleasanter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pleasanter MCP Server, 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.
9 Pleasanter MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.