Retrieve activity logs for the account.
AI agents call pressable_get_account_activity_logs to retrieve information from Pressable 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 account activity logs, which is a read operation with no side effects. It allows viewing historical activity but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an attacker could view activity history but cannot alter systems or data based on this tool alone.
From the tool's definition Tool name includes 'get' and description states 'Retrieve activity logs' - both indicate a read-only operation that queries existing data without modification.
Attacks that exploit this kind of access
Retrieve activity logs for the account. It is categorised as a Read tool in the Pressable MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pressable MCP Server MCP server in PolicyLayer and add a rule for pressable_get_account_activity_logs: 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 Pressable MCP Server. Nothing to install.
pressable_get_account_activity_logs 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 pressable_get_account_activity_logs 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 pressable_get_account_activity_logs. 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.
pressable_get_account_activity_logs is provided by the Pressable MCP Server MCP server (pcwprops/pressable-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 →