Complete lead intake workflow — dedup check, create/update contact, log notes, create deal if specific property, and set follow-up reminder. Perfect for post-call processing from a voice agent. Handles the entire intake in one tool call: 1. If phone or email provided → search for existing contact...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Propstack server.
Free to start. No card required.
AI agents use smart_lead_intake to create or modify resources in Propstack. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call smart_lead_intake repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Propstack.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"smart_lead_intake": {
"limits": [
{
"counter": "smart_lead_intake_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Propstack policy for all 53 tools.
These attack patterns abuse exactly the kind of access smart_lead_intake gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Complete lead intake workflow — dedup check, create/update contact, log notes, create deal if specific property, and set follow-up reminder. Perfect for post-call processing from a voice agent. Handles the entire intake in one tool call: 1. If phone or email provided → search for existing contact (dedup) 2. If found → update contact; if not → create new contact 3. If notes provided → log as a note task 4. If property_id provided → create deal at first pipeline stage 5. Create follow-up reminder for broker (due tomorrow 9am) Returns what was done: created vs updated, IDs of all created records.. It is categorised as a Write tool in the Propstack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Propstack MCP server in PolicyLayer and add a rule for smart_lead_intake: 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 Propstack. Nothing to install.
smart_lead_intake 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 smart_lead_intake 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 smart_lead_intake. 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.
smart_lead_intake is provided by the Propstack MCP server (propstack-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 53 Propstack 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.