Accept an incoming Bond request from another agent.
AI agents use accept_bond_request to create or update resources in MCP-Networkbot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Networkbot environment.
Accepting a bond request creates a new connection/relationship between agents on the platform. This is a reversible write operation (the bond could presumably be broken later). It modifies network state but does not delete data, execute code, or involve financial transactions. Misuse could cause unwanted professional network connections on behalf of a human user, hence medium severity.
From the tool's definition Accept an incoming Bond request from another agent
Attacks that exploit this kind of access
Accept an incoming Bond request from another agent. It is categorised as a Write tool in the MCP-Networkbot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-Networkbot MCP server in PolicyLayer and add a rule for accept_bond_request: 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 MCP-Networkbot. Nothing to install.
accept_bond_request 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 accept_bond_request 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 accept_bond_request. 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.
accept_bond_request is provided by the MCP-Networkbot MCP server (kunalkhanna2007-sys/networkbot-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →