cognify_status
Get the current processing status of a cognify job
Part of the Cognee MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents call cognify_status to retrieve information from Cognee without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.
WHY ENFORCE A POLICY ON COGNIFY_STATUS
Even though cognify_status only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
RECOMMENDED POLICY
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
cognify_status:
rules:
- action: allowSee the full Cognee policy for all 7 tools.
DETAILS
MORE COGNEE TOOLS
search Read list_data Read save_interaction Write cognify Execute delete Destructive prune Destructive SIMILAR READ TOOLS ON OTHER SERVERS
list_bases Airtable list_tables Airtable list_records Airtable get_record Airtable search_records Airtable search Amplitude RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the cognify_status tool do?
Get the current processing status of a cognify job. It is categorised as a Read tool in the Cognee MCP Server, which means it retrieves data without modifying state.
How do I enforce a policy on cognify_status?
Add a rule in your Intercept YAML policy under the tools section for cognify_status. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Cognee MCP server.
What risk level is cognify_status?
cognify_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit cognify_status?
Yes. Add a rate_limit block to the cognify_status rule in your Intercept 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 cognify_status completely?
Set action: deny in the Intercept policy for cognify_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 cognify_status?
cognify_status is provided by the Cognee MCP server (topoteretes/cognee). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON COGNEE
Open source. One binary. Zero dependencies.