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).
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.
This tool primarily modifies and creates knowledge base resource entries (Write category), but includes a delete capability. The delete action on knowledge base entries warrants medium severity rather than high because it operates on structured resource metadata within articles rather than critical system data, and the scope appears limited to knowledge base management.
From the tool's definition Tool performs actions including 'add, edit, list, delete, flag...verify...dismiss' on knowledge base resources. The 'delete' action is destructive but appears scoped to resource entries within a knowledge base article rather than system-wide data.
Documented attack patterns abuse exactly the kind of access crow_kb_manage_resources 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_kb_manage_resources:
{
"version": "1",
"default": "deny",
"tools": {
"crow_kb_manage_resources": {
"limits": [
{
"counter": "crow_kb_manage_resources_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.