GET ORDER VALUE HISTORY - Get a history of an order
AI agents call tiendanube_get_order_value_history 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 queries historical data about order values. It retrieves information without creating, modifying, deleting, executing code, or affecting financial transactions. The read-only nature and limited scope (viewing historical data only) present minimal risk if misused by an AI agent.
From the tool's definition Tool name includes 'get' and description states 'Get a history of an order' — pure retrieval with no modification or side effects.
Attacks that exploit this kind of access
GET ORDER VALUE HISTORY - Get a history of an order. 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_order_value_history: 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_order_value_history 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_order_value_history 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_order_value_history. 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_order_value_history 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 →