Generate outreach copy (email or LinkedIn message) grounded in prospect evidence from SEC filings. Stakeholder role data from get_dealmap enables role-aware outreach personalization (e.g., ROI for Economic Buyers, capability fit for Decision Makers). Optional lead personalization supports either ...
Part of the Dealsurface server.
Free to start. No card required.
AI agents call craft_outreach to retrieve information from Dealsurface 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 craft_outreach 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": {
"craft_outreach": {}
}
}See the full Dealsurface policy for all 9 tools.
These attack patterns abuse exactly the kind of access craft_outreach 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.
Generate outreach copy (email or LinkedIn message) grounded in prospect evidence from SEC filings. Stakeholder role data from get_dealmap enables role-aware outreach personalization (e.g., ROI for Economic Buyers, capability fit for Decision Makers). Optional lead personalization supports either selected_lead (full stakeholder object from get_dealmap response) or lead_selector ({node_id} | {level} | {full_name+level} | {stakeholder_role}). If both are supplied, selected_lead takes precedence. When selector matching fails, response includes selected_lead_note guidance. Billed operation: credits are only charged when a valid result is returned. Requires. It is categorised as a Read tool in the Dealsurface MCP Server, which means it retrieves data without modifying state.
Register the Dealsurface MCP server in PolicyLayer and add a rule for craft_outreach: 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 Dealsurface. Nothing to install.
craft_outreach 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 craft_outreach 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 craft_outreach. 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.
craft_outreach is provided by the Dealsurface MCP server (@dealsurface/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Dealsurface 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.