get_subscription_by_id
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-subscription-by-id.md
What get_subscription_by_id does on PineLabs Plural PG — Payment Gateway MCP Server
AI agents call get_subscription_by_id 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_subscription_by_id is rated Low
The 'get' prefix and '_by_id' suffix strongly indicate a read/retrieval operation without side effects. However, subscription data in payment systems is sensitive (contains financial and PII records), elevating severity from low to medium. Confidence is moderate (0.75) because the description is empty, leaving some ambiguity about what data is actually returned and any undocumented side effects.
From the tool's definition Tool name 'get_subscription_by_id' indicates retrieval of subscription data by identifier. No description provided, but naming convention and sibling tools (create_*, cancel_*, etc.) suggest this queries payment subscription records.
Attacks that exploit this kind of access
The rule that runs get_subscription_by_id 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_subscription_by_id, this is the rule to start with:
get_subscription_by_id 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_subscription_by_id call is checked against it from then on.
Questions about get_subscription_by_id
get_subscription_by_id 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_subscription_by_id: 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_subscription_by_id 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_subscription_by_id 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_subscription_by_id. 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_subscription_by_id 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