list_ownershipaccounts_associations_recurringtransactions
Retrieves all recurring transactions for an ownership account.\r\n \r\n\r\n<h4>Required permission(s):</h4><span class=
This record as markdown: /tools/wpm-mcp-server/list-ownershipaccounts-associations-recurringtransactions.md
What list_ownershipaccounts_associations_recurringtransactions does on Wpm Mcp Server
AI agents call list_ownershipaccounts_associations_recurringtransactions to retrieve information from Wpm Mcp Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_ownershipaccounts_associations_recurringtransactions is rated Low
This tool queries and returns recurring transaction data for an ownership account without creating, modifying, deleting, or executing any operations. It is a read-only operation with minimal risk. Although the broader server handles financial operations (payments, refunds, charges), this specific tool only retrieves information.
From the tool's definition Tool name contains 'list_' prefix and description states 'Retrieves all recurring transactions' — both indicate data retrieval with no modification.
Attacks that exploit this kind of access
The rule that runs list_ownershipaccounts_associations_recurringtransactions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wpm Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_ownershipaccounts_associations_recurringtransactions, this is the rule to start with:
list_ownershipaccounts_associations_recurringtransactions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Wpm Mcp Server, apply this rule, and every list_ownershipaccounts_associations_recurringtransactions call is checked against it from then on.
Questions about list_ownershipaccounts_associations_recurringtransactions
Retrieves all recurring transactions for an ownership account.\r\n \r\n\r\n<h4>Required permission(s):</h4><span class=. It is categorised as a Read tool in the Wpm Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Wpm Mcp Server MCP server in PolicyLayer and add a rule for list_ownershipaccounts_associations_recurringtransactions: 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 Wpm Mcp Server. Nothing to install.
list_ownershipaccounts_associations_recurringtransactions 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 list_ownershipaccounts_associations_recurringtransactions 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 list_ownershipaccounts_associations_recurringtransactions. 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.
list_ownershipaccounts_associations_recurringtransactions is provided by the Wpm Mcp Server MCP server (wpm-mcp-server-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wpm Mcp Server, and thousands of servers like it.
This server
Across the catalogue