Query records from any Gadget model. Supports filtering, sorting, pagination cursors, and field selection. Use introspect_model first to discover available fields, and introspect_filters to see valid filter shapes.
AI agents call query_records 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 performs data retrieval operations only. It queries records with various parameters (filtering, sorting, pagination) but does not modify, delete, or execute operations. The read-only nature of the server and the query-only capability clearly place this in the Read category with low severity, as misuse would only expose data rather than cause irreversible harm or execute arbitrary code.
From the tool's definition Tool description states 'Query records from any Gadget model' with support for 'filtering, sorting, pagination cursors, and field selection.' The server is explicitly described as 'read-only MCP server.' No mention of create, update, delete, or execute…
Attacks that exploit this kind of access
Query records from any Gadget model. Supports filtering, sorting, pagination cursors, and field selection. Use introspect_model first to discover available fields, and introspect_filters to see valid filter shapes. 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 query_records: 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.
query_records 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 query_records 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 query_records. 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.
query_records 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 →