get_status · Graphiti Knowledge Graph MCP Server MCP

WHAT IT DOES

What get_status does on Graphiti Knowledge Graph MCP Server

AI agents call get_status to retrieve information from Graphiti Knowledge Graph MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why get_status needs a policy

This tool performs a read-only operation to check server and database connection status. It has no side effects, does not modify data, and does not execute commands. The minimal blast radius of a misused status check is negligible—an agent cannot cause harm by querying status information repeatedly or unnecessarily.

From the tool's definition Tool name 'get_status' and description 'Get the status of the Graphiti MCP server and Neo4j connection' indicate a query operation that retrieves status information without modifying any data or triggering external operations.

Documented attack patterns abuse exactly the kind of access get_status gives an agent:

POLICY

How to control get_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Graphiti Knowledge Graph MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_status:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_status": {}
  }
}

get_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Graphiti Knowledge Graph MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Graphiti Knowledge Graph MCP Server tools

Destructive clear_graph Clear all data from the knowledge graph and rebuild indices. Requires password authenticat Destructive delete_entity_edge Delete an entity edge from the knowledge graph Destructive delete_episode Delete an episode from the knowledge graph Destructive delete_everything_by_group_id Delete all data (episodes, nodes, and entity edges) associated with a group_id. This is an Write add_episode Add an episode to the knowledge graph (supports text, JSON, and message formats) Read get_entity_edge Get an entity edge by its UUID Read get_episodes Get the most recent episodes for a specific group Read get_queue_status Get the current status of all episode processing queues. Shows total pending tasks, active

All 11 Graphiti Knowledge Graph MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_status

What does the get_status tool do? +

Get the status of the Graphiti MCP server and Neo4j connection. It is categorised as a Read tool in the Graphiti Knowledge Graph MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_status? +

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

What risk level is get_status? +

get_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_status? +

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

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

get_status is provided by the Graphiti Knowledge Graph MCP Server MCP server (michabbb/graphiti-mcp-but-working). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Graphiti Knowledge Graph MCP Server tool call.

Start from Graphiti Knowledge Graph MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

11 Graphiti Knowledge Graph MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.