oc_list_transactions
AI agents call oc_list_transactions to retrieve information from OpenCollective MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
List and query operations retrieve data without modifying, deleting, or executing code. Even in a financial context (OpenCollective transaction management), listing transactions is purely informational—it does not move money, create obligations, or alter records. The severity is low because misuse would only expose financial data, not cause financial loss or irreversible damage.
From the tool's definition Tool name 'oc_list_transactions' indicates a list/query operation typical of Read category. The server description confirms it 'enables AI agents to manage expenses, query transactions' with 'query transactions' being a Read operation.
Attacks that exploit this kind of access
oc_list_transactions. It is categorised as a Read tool in the OpenCollective MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenCollective MCP Server MCP server in PolicyLayer and add a rule for oc_list_transactions: 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 OpenCollective MCP Server. Nothing to install.
oc_list_transactions 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 oc_list_transactions 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 oc_list_transactions. 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.
oc_list_transactions is provided by the OpenCollective MCP Server MCP server (theepicsaxguy/opencollective-hetzner-mcp). 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 →