AI agents call get_project_note_activity_log to retrieve information from Repsona without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves historical activity data about project notes. It queries existing information without modifying, deleting, executing code, or affecting financial systems. This is a standard Read operation with low severity since activity logs typically contain non-sensitive audit information, though severity could be medium if logs expose sensitive user actions or system details.
From the tool's definition Tool name 'get_project_note_activity_log' and description state it 'retrieves activity log' (アクティビティログを取得します means 'retrieves activity log') for notes within a project. This is a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
指定したプロジェクト内のノートのアクティビティログを取得します. It is categorised as a Read tool in the Repsona MCP Server, which means it retrieves data without modifying state.
Register the Repsona MCP server in PolicyLayer and add a rule for get_project_note_activity_log: 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 Repsona. Nothing to install.
get_project_note_activity_log 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 get_project_note_activity_log 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 get_project_note_activity_log. 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.
get_project_note_activity_log is provided by the Repsona MCP server (@bellx2/repsona-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 →