GET METAFIELD - Retrieve a single metafield by ID.
AI agents call tiendanube_get_metafield 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 retrieves metafield data without modifying, deleting, or executing any operations. It is a straightforward read operation against the Tienda Nube API. The blast radius of misuse is minimal, as it only exposes existing metadata. Confidence is high because the description unambiguously indicates a GET operation with no mutations.
From the tool's definition Tool name contains 'get' and description explicitly states 'Retrieve a single metafield by ID' — a pure data retrieval operation with no side effects.
Attacks that exploit this kind of access
GET METAFIELD - Retrieve a single metafield 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_metafield: 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_metafield 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_metafield 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_metafield. 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_metafield 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 →