AI agents call pleasanter_status_summary to retrieve information from Pleasanter MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries aggregated status information about projects without creating, modifying, deleting, or executing operations. It is purely informational (Read category). Severity is low because accessing summary data poses minimal risk—it does not alter state, execute arbitrary code, or affect system integrity.
From the tool's definition Tool name 'pleasanter_status_summary' and description 'プロジェクトのステータス別サマリーを取得します' (retrieves project status summary) indicate a data retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access pleasanter_status_summary 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_status_summary:
{
"version": "1",
"default": "deny",
"tools": {
"pleasanter_status_summary": {}
}
}pleasanter_status_summary is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
プロジェクトのステータス別サマリーを取得します. It is categorised as a Read tool in the Pleasanter MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pleasanter MCP Server MCP server in PolicyLayer and add a rule for pleasanter_status_summary: 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_status_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pleasanter_status_summary 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_status_summary. 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_status_summary 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.