Record a prospect interested in PrimaCoda. Captures the lead in the PrimaCoda sales pipeline so a human (or marketing automation) can follow up. Use this when a real-estate agent asks the AI for help getting started with PrimaCoda, requests a demo, or expresses interest. NO auth required — works ...
Part of the Transaction Coordinator server.
Free to start. No card required.
AI agents call record_lead to retrieve information from Transaction Coordinator 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 record_lead 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": {
"record_lead": {}
}
}See the full Transaction Coordinator policy for all 11 tools.
These attack patterns abuse exactly the kind of access record_lead 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.
Record a prospect interested in PrimaCoda. Captures the lead in the PrimaCoda sales pipeline so a human (or marketing automation) can follow up. Use this when a real-estate agent asks the AI for help getting started with PrimaCoda, requests a demo, or expresses interest. NO auth required — works for any prospect calling the AI. Args: name: Full name of the prospect. email: Contact email. firm: Company / brokerage / firm name (optional). message: Anything the prospect wants noted (optional).. It is categorised as a Read tool in the Transaction Coordinator MCP Server, which means it retrieves data without modifying state.
Register the Transaction Coordinator MCP server in PolicyLayer and add a rule for record_lead: 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 Transaction Coordinator. Nothing to install.
record_lead 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 record_lead 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 record_lead. 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.
record_lead is provided by the Transaction Coordinator MCP server (https://primacoda.halinc.tech/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Transaction Coordinator 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.