GET PAYMENT OPTION - Retrieve a payment option by ID.
AI agents call tiendanube_get_payment_option to retrieve information from Tienda Nube MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple retrieval operation. It queries and returns payment option data by ID without side effects, matching the definition of a Read category tool. The severity is low because retrieving payment configuration data poses minimal risk even if accessed by an AI agent without authorization.
From the tool's definition Tool name contains 'get' and description states 'Retrieve a payment option by ID' — classic read operation with no data modification, deletion, or execution.
Attacks that exploit this kind of access
GET PAYMENT OPTION - Retrieve a payment option by ID. It is categorised as a Read tool in the Tienda Nube MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tienda Nube MCP Server MCP server in PolicyLayer and add a rule for tiendanube_get_payment_option: 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 Tienda Nube MCP Server. Nothing to install.
tiendanube_get_payment_option 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 tiendanube_get_payment_option 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 tiendanube_get_payment_option. 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.
tiendanube_get_payment_option is provided by the Tienda Nube MCP Server MCP server (pedrohsguimaraes/nuvem-shop-mcp-server). 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 →