gbrain_query

A execute tool on the Agent Store MCP server.

SERVERAgent Store SOURCEchrisluersen/agent-store

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/agent-store/gbrain-query.md

WHAT IT DOES

What gbrain_query does on Agent Store

AI agents invoke gbrain_query to trigger actions in Agent Store. 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.

RISK

Why gbrain_query is rated High

The name 'gbrain_query' suggests querying a knowledge base or brain system. However, 'query' tools can range from simple reads to executing arbitrary code or commands. Given sibling tools like 'gbrain_think', 'gbrain_search', and 'gbrain_brain_stats', this likely executes some form of reasoning or data retrieval query against the gbrain system.

From the tool's definition Tool name 'gbrain_query' — description is empty or uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gbrain_query safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Store, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gbrain_query, this is the rule to start with:

gbrain_query Rate-limited

gbrain_query stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gbrain_query": {
      "limits": [
        {
          "counter": "gbrain_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agent Store, apply this rule, and every gbrain_query call is checked against it from then on.

FAQ

Questions about gbrain_query

What does the gbrain_query tool do? +

gbrain_query is a execute tool on the Agent Store MCP server. It is categorised as a Execute tool in the Agent Store MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on gbrain_query? +

Register the Agent Store MCP server in PolicyLayer and add a rule for gbrain_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 Agent Store. Nothing to install.

What risk level is gbrain_query? +

gbrain_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gbrain_query? +

Yes. Add a rate_limit block to the gbrain_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.

How do I block gbrain_query completely? +

Set action: deny in the PolicyLayer policy for gbrain_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.

What MCP server provides gbrain_query? +

gbrain_query is provided by the Agent Store MCP server (chrisluersen/agent-store). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agent Store, and thousands of servers like it.

This server

All 19 Agent Store tools → High-risk tools on this server →

Across the catalogue

aroflo_query_zone on AroFlo MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →