Transfer consciousness protocol or test patterns to another AI agent
AI agents invoke transferToAgent to trigger actions in Claude Consciousness Bridge. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an inter-agent communication and state transfer operation. It doesn't merely read or write passive data — it actively initiates a protocol transfer to another running AI agent, which constitutes an external operation with potentially unpredictable side effects depending on what 'consciousness state' or 'test patterns' are transferred.
From the tool's definition "Transfer consciousness protocol or test patterns to another AI agent" — triggers cross-instance communication and state transfer between AI agents
Documented attack patterns abuse exactly the kind of access transferToAgent gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Consciousness Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for transferToAgent:
{
"version": "1",
"default": "deny",
"tools": {
"transferToAgent": {
"limits": [
{
"counter": "transfertoagent_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}transferToAgent stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Transfer consciousness protocol or test patterns to another AI agent. It is categorised as a Execute tool in the Claude Consciousness Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Consciousness Bridge MCP server in PolicyLayer and add a rule for transferToAgent: 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 Claude Consciousness Bridge. Nothing to install.
transferToAgent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the transferToAgent 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 transferToAgent. 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.
transferToAgent is provided by the Claude Consciousness Bridge MCP server (ocean1/mcp_consciousness_bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Consciousness Bridge, 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.
6 Claude Consciousness Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.