Open a metered payment tab with a service provider. The provider can charge per-unit (per API call, per token, per query, etc.) up to your spend limit.
AI agents use open_tab to commit financial operations through Remit Md MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool initiates a financial arrangement where a third-party provider can repeatedly charge the agent per unit of usage up to a defined spend limit. It commits financial obligations on behalf of the user, making it a Financial category tool.
From the tool's definition 'Open a metered payment tab with a service provider. The provider can charge per-unit (per API call, per token, per query, etc.) up to your spend limit.'
Attacks that exploit this kind of access
Open a metered payment tab with a service provider. The provider can charge per-unit (per API call, per token, per query, etc.) up to your spend limit. It is categorised as a Financial tool in the Remit Md MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Remit Md MCP Server MCP server in PolicyLayer and add a rule for open_tab: 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 Remit Md MCP Server. Nothing to install.
open_tab is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the open_tab 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 open_tab. 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.
open_tab is provided by the Remit Md MCP Server MCP server (pay-skill/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 →