AI agents call pleasanter_trend_analysis 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.
The tool retrieves and analyzes historical project data to provide insights and trends. This is a classic Read operation: it queries data without side effects, creates no new records, executes no commands, and makes no modifications. The low severity reflects that misuse would only expose analytics information, not compromise data integrity or trigger external operations.
From the tool's definition Tool description indicates it performs trend analysis on project metrics (completion rates, creation counts, update counts, etc.) - these are read-only analytical operations that retrieve and aggregate existing data without modifying or executing any actions.
Documented attack patterns abuse exactly the kind of access pleasanter_trend_analysis 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_trend_analysis:
{
"version": "1",
"default": "deny",
"tools": {
"pleasanter_trend_analysis": {}
}
}pleasanter_trend_analysis 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_trend_analysis: 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_trend_analysis 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_trend_analysis 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_trend_analysis. 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_trend_analysis 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.