Query entities from Datastore with optional filters, ordering, and pagination
AI agents call datastore_query to retrieve information from MCP Datastore Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves entities from Datastore based on query parameters. It reads data without modifying it. Severity is medium because it could expose sensitive data if misused, and pagination/filter parameters could allow broad data access across the datastore.
From the tool's definition Query entities from Datastore with optional filters, ordering, and pagination
Attacks that exploit this kind of access
Query entities from Datastore with optional filters, ordering, and pagination. It is categorised as a Read tool in the MCP Datastore Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Datastore Server MCP server in PolicyLayer and add a rule for datastore_query: 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 MCP Datastore Server. Nothing to install.
datastore_query 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 datastore_query 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 datastore_query. 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.
datastore_query is provided by the MCP Datastore Server MCP server (petekmet/mcp-gcp-datastore). 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 →