get_subscriptions
A read tool on the PineLabs Plural PG — Payment Gateway MCP server.
This record as markdown: /tools/io-github-plural-pinelabs-pinelabs-online-mcp/get-subscriptions.md
What get_subscriptions does on PineLabs Plural PG — Payment Gateway MCP Server
AI agents call get_subscriptions to retrieve information from PineLabs Plural PG — Payment Gateway 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 get_subscriptions is rated Low
Despite the empty description, the tool name 'get_subscriptions' indicates a retrieval operation that queries subscription data without modifying state. However, this is classified as medium severity rather than low because subscriptions on a payment gateway are sensitive financial information—unauthorized access could expose payment preferences, billing cycles, and customer financial commitments.
From the tool's definition Tool name is 'get_subscriptions' which follows the 'get' pattern indicating a retrieval operation. The sibling tools on this payment gateway server include create, cancel, and capture operations, establishing context that this server handles financial…
Attacks that exploit this kind of access
The rule that runs get_subscriptions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and PineLabs Plural PG — Payment Gateway MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_subscriptions, this is the rule to start with:
get_subscriptions 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 PineLabs Plural PG — Payment Gateway MCP Server, apply this rule, and every get_subscriptions call is checked against it from then on.
Questions about get_subscriptions
get_subscriptions is a read tool on the PineLabs Plural PG — Payment Gateway MCP Server MCP server. It is categorised as a Read tool in the PineLabs Plural PG — Payment Gateway MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PineLabs Plural PG — Payment Gateway MCP Server MCP server in PolicyLayer and add a rule for get_subscriptions: 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 PineLabs Plural PG — Payment Gateway MCP Server. Nothing to install.
get_subscriptions 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_subscriptions 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_subscriptions. 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_subscriptions is provided by the PineLabs Plural PG — Payment Gateway MCP Server MCP server (pypi:pinelabs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on PineLabs Plural PG — Payment Gateway MCP Server, and thousands of servers like it.
Across the catalogue