Get a single Gadget record by ID. Specify the model name, record ID, and fields to return.
AI agents call get_record to retrieve information from Gadget 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 a single record from a Gadget app via GraphQL query. It has no side effects—no data is created, modified, deleted, or overwritten. The user specifies which fields to return, making it a straightforward data retrieval operation. The read-only nature of the server confirms this is a Read category tool with low severity.
From the tool's definition Tool description explicitly states 'Get a single Gadget record by ID' and server is described as 'read-only MCP server'. The operation retrieves data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get a single Gadget record by ID. Specify the model name, record ID, and fields to return. It is categorised as a Read tool in the Gadget MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Gadget MCP Server MCP server in PolicyLayer and add a rule for get_record: 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 Gadget MCP Server. Nothing to install.
get_record 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_record 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_record. 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_record is provided by the Gadget MCP Server MCP server (stronger-ecommerce/gadget-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 →