Add a knowledge entry to the Black Box. Requires master token. Only in ACTIVE phase. Categories: finances, contacts, accounts, documents, decisions, commitments, medical, other.
AI agents use contribute_knowledge to create or update resources in WAKE Protocol — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WAKE Protocol environment.
An AI agent can call contribute_knowledge faster than any human can review — one bad instruction and it creates or modifies resources in WAKE Protocol by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Add a knowledge entry to the Black Box. Requires master token. Only in ACTIVE phase. Categories: finances, contacts, accounts, documents, decisions, commitments, medical, other. It is categorised as a Write tool in the WAKE Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WAKE Protocol MCP server in PolicyLayer and add a rule for contribute_knowledge: 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 WAKE Protocol. Nothing to install.
contribute_knowledge 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 contribute_knowledge 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 contribute_knowledge. 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.
contribute_knowledge is provided by the WAKE Protocol MCP server (wake-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.