List all crow.md sections with their metadata (key, title, sort order, enabled status, device/project scope). Does not return full content — use crow_get_context for that.
AI agents call crow_list_context_sections to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves metadata about context sections in a project management system. It has no side effects, does not modify data, and cannot cause harm beyond potentially exposing non-sensitive metadata. The explicit note that it doesn't return full content further constrains its scope to basic informational retrieval, consistent with the Read category.
From the tool's definition Tool description explicitly states it 'List all crow.md sections with their metadata' and 'Does not return full content'. The action is listing/retrieving metadata only, with no modification, deletion, or execution of commands.
Documented attack patterns abuse exactly the kind of access crow_list_context_sections gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_list_context_sections:
{
"version": "1",
"default": "deny",
"tools": {
"crow_list_context_sections": {}
}
}crow_list_context_sections is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all crow.md sections with their metadata (key, title, sort order, enabled status, device/project scope). Does not return full content — use crow_get_context for that. 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_list_context_sections: 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_list_context_sections 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_list_context_sections 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_list_context_sections. 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_list_context_sections 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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.