Build and run structured queries against AllianceMine using a JSON DSL. Example query - find human genes in DNA repair pathway: {
AI agents invoke mine_query_builder to trigger actions in AGR MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Although the server is read-oriented (genomics data retrieval), this tool accepts a flexible JSON DSL and executes it against AllianceMine. The ability to 'build and run' arbitrary structured queries introduces execution-level risk: a malformed or malicious query could trigger unintended data access patterns, resource exhaustion, or expose sensitive data beyond the intended scope.
From the tool's definition 'Build and run structured queries against AllianceMine using a JSON DSL' — the tool both constructs and executes queries using an arbitrary JSON DSL, meaning it actively runs structured queries against a database backend, not merely reading pre-defined data.
Attacks that exploit this kind of access
Build and run structured queries against AllianceMine using a JSON DSL. Example query - find human genes in DNA repair pathway: {. It is categorised as a Execute tool in the AGR MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AGR MCP Server MCP server in PolicyLayer and add a rule for mine_query_builder: 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 AGR MCP Server. Nothing to install.
mine_query_builder is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mine_query_builder 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 mine_query_builder. 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.
mine_query_builder is provided by the AGR MCP Server MCP server (nuin/agr-mcp-server-js). 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 →