Return the total number of records for a Gadget model, with optional filtering.
AI agents call count_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 retrieves aggregate data (record count) from a Gadget app model. It has no side effects, does not create, modify, or delete data, and does not execute external operations. It is a straightforward read operation that fits the 'Read' category (retrieves or queries data; no side effects). Severity is low because miscounting records poses minimal risk; the blast radius of misuse is negligible.
From the tool's definition Tool description states it 'Return[s] the total number of records' with 'optional filtering'. Server description emphasizes this is a 'read-only MCP server that enables querying and introspection'.
Attacks that exploit this kind of access
Return the total number of records for a Gadget model, with optional filtering. 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 count_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.
count_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 count_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 count_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.
count_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 →