crow_get_context
Generate and return the full crow.md cross-platform behavioral context document. This document defines how Crow behaves across all AI platforms — personality, memory protocols, transparency rules, and more. Includes optional dynamic data (memory stats, active projects, preferences). Use device_id...
This record as markdown: /tools/kh0pper-crow/crow-get-context.md
What crow_get_context does on Crow
AI agents call crow_get_context to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crow_get_context is rated Low
This tool retrieves and generates contextual configuration/behavioral data without creating, modifying, or deleting anything. However, the 'medium' severity reflects that the returned context document may contain sensitive behavioral protocols, memory statistics, and user preferences that could inform social engineering or manipulation if accessed by a malicious actor, particularly given the system handles…
From the tool's definition Tool description states 'Generate and return the full crow.md cross-platform behavioral context document.' The verb 'return' and action of retrieving a document, along with optional 'dynamic data (memory stats, active projects, preferences)' retrieval,…
Attacks that exploit this kind of access
The rule that runs crow_get_context safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_get_context, this is the rule to start with:
crow_get_context is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_get_context call is checked against it from then on.
Questions about crow_get_context
Generate and return the full crow.md cross-platform behavioral context document. This document defines how Crow behaves across all AI platforms — personality, memory protocols, transparency rules, and more. Includes optional dynamic data (memory stats, active projects, preferences). Use device_id to get device-specific overrides merged with global context. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_get_context: 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 Crow. Nothing to install.
crow_get_context is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the crow_get_context 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 crow_get_context. 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.
crow_get_context is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue