release_lead_from_outbound

Take a lead back out of Outbound — below the line on /targets, out of Pipeline\

SERVERAdrata SOURCE@adrata/adrata-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-adrata-mcp/release-lead-from-outbound.md

WHAT IT DOES

What release_lead_from_outbound does on Adrata

AI agents call release_lead_from_outbound to retrieve information from Adrata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why release_lead_from_outbound is rated Low

Even though release_lead_from_outbound only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs release_lead_from_outbound safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For release_lead_from_outbound, this is the rule to start with:

release_lead_from_outbound Allowed

release_lead_from_outbound is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "release_lead_from_outbound": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every release_lead_from_outbound call is checked against it from then on.

FAQ

Questions about release_lead_from_outbound

What does the release_lead_from_outbound tool do? +

Take a lead back out of Outbound — below the line on /targets, out of Pipeline\. It is categorised as a Read tool in the Adrata MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on release_lead_from_outbound? +

Register the Adrata MCP server in PolicyLayer and add a rule for release_lead_from_outbound: 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 Adrata. Nothing to install.

What risk level is release_lead_from_outbound? +

release_lead_from_outbound is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit release_lead_from_outbound? +

Yes. Add a rate_limit block to the release_lead_from_outbound 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.

How do I block release_lead_from_outbound completely? +

Set action: deny in the PolicyLayer policy for release_lead_from_outbound. 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.

What MCP server provides release_lead_from_outbound? +

release_lead_from_outbound is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Adrata, and thousands of servers like it.

This server

All 395 Adrata tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →