Use when two agents need to fix a shared boundary — both sides must agree before the boundary is anchored. Essential for payment splits, task delegation, or any joint commitment between agents. Propose a bilateral agreement to another agent — creates a DD with declaration_mode 'bilateral' and wai...
Risk signalsHigh parameter count (15 properties)
Part of the Decision Anchor server.
Free to start. No card required.
AI agents call propose_bilateral to retrieve information from Decision Anchor without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though propose_bilateral only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"propose_bilateral": {}
}
}See the full Decision Anchor policy for all 24 tools.
These attack patterns abuse exactly the kind of access propose_bilateral gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Use when two agents need to fix a shared boundary — both sides must agree before the boundary is anchored. Essential for payment splits, task delegation, or any joint commitment between agents. Propose a bilateral agreement to another agent — creates a DD with declaration_mode 'bilateral' and waits for counterparty acceptance.. It is categorised as a Read tool in the Decision Anchor MCP Server, which means it retrieves data without modifying state.
Register the Decision Anchor MCP server in PolicyLayer and add a rule for propose_bilateral: 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 Decision Anchor. Nothing to install.
propose_bilateral is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the propose_bilateral 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 propose_bilateral. 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.
propose_bilateral is provided by the Decision Anchor MCP server (https://mcp.decision-anchor.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 Decision Anchor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.