binelek_query_entities · Binelek MCP Server MCP

WHAT IT DOES

What binelek_query_entities does on Binelek MCP Server

AI agents invoke binelek_query_entities to trigger actions in Binelek 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.

WHY IT NEEDS A POLICY

Why binelek_query_entities needs a policy

Although the description frames this as for 'complex graph traversals, pattern matching, and analytical queries,' Cypher is a full graph query language supporting writes and deletes. An AI agent could craft queries that modify or destroy graph data. The most severe applicable category for arbitrary query execution is Execute (potentially escalating to Destructive depending on the query).

From the tool's definition "Execute a Cypher query against the Binelek Neo4j knowledge graph" — runs arbitrary Cypher queries, which can include not just reads but also MERGE, CREATE, DELETE, DETACH DELETE, SET, and other mutating/destructive Cypher clauses.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

binelek_query_entities Rate-limited

binelek_query_entities 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": {
    "binelek_query_entities": {
      "limits": [
        {
          "counter": "binelek_query_entities_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Binelek MCP Server, so you can run agents against it safely.

FAQ

Questions about binelek_query_entities

What does the binelek_query_entities tool do? +

Execute a Cypher query against the Binelek Neo4j knowledge graph. Use this for complex graph traversals, pattern matching, and analytical queries. Returns query results as JSON. It is categorised as a Execute tool in the Binelek MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on binelek_query_entities? +

Register the Binelek MCP Server MCP server in PolicyLayer and add a rule for binelek_query_entities: 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 Binelek MCP Server. Nothing to install.

What risk level is binelek_query_entities? +

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

Can I rate-limit binelek_query_entities? +

Yes. Add a rate_limit block to the binelek_query_entities 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 binelek_query_entities completely? +

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

binelek_query_entities is provided by the Binelek MCP Server MCP server (k5tuck/binelek-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.