query_records
Query records from a collection. Filter by field values, sort, paginate.
This record as markdown: /tools/io-github-proagentstore-platform/query-records.md
What query_records does on ProAgentStore
AI agents call query_records to retrieve information from ProAgentStore without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why query_records is rated Low
This tool performs read-only operations on stored records using standard query parameters (filter, sort, paginate). There are no side effects, no data modification, and no irreversible actions. It falls squarely into the Read category with low severity due to the minimal blast radius of querying data alone.
From the tool's definition Tool name 'query_records' and description 'Query records from a collection. Filter by field values, sort, paginate.' indicate data retrieval with filtering and pagination—no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs query_records safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query_records, this is the rule to start with:
query_records is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every query_records call is checked against it from then on.
Questions about query_records
Query records from a collection. Filter by field values, sort, paginate. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.
Register the ProAgentStore 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 ProAgentStore. 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 ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
This server
Across the catalogue