crow_kb_manage_resources
Manage structured resource entries for a knowledge base article. Actions: add, edit, list, delete, flag (AI marks as potentially outdated), verify (human confirms current), dismiss (dismiss a flag).
This record as markdown: /tools/kh0pper-crow/crow-kb-manage-resources.md
What crow_kb_manage_resources does on Crow
AI agents use crow_kb_manage_resources to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Why crow_kb_manage_resources is rated Medium
While the tool includes a delete action, it operates on knowledge base resource entries within a managed article context, not on irreversible system-level data or core project data. The presence of complementary actions (flag, verify, dismiss) suggests a reversible workflow.
From the tool's definition Tool description states actions include: add, edit, list, delete, flag, verify, dismiss. The 'delete' action is present but framed as part of a broader resource management suite that includes reversible operations (add, edit, flag, verify, dismiss).
Attacks that exploit this kind of access
The rule that runs crow_kb_manage_resources 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_kb_manage_resources, this is the rule to start with:
crow_kb_manage_resources stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_kb_manage_resources call is checked against it from then on.
Questions about crow_kb_manage_resources
Manage structured resource entries for a knowledge base article. Actions: add, edit, list, delete, flag (AI marks as potentially outdated), verify (human confirms current), dismiss (dismiss a flag). It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for crow_kb_manage_resources: 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_kb_manage_resources is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the crow_kb_manage_resources 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_kb_manage_resources. 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_kb_manage_resources 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