Send an email using a Propstack email template (snippet). Propstack sends emails through connected broker email accounts. The broker_id determines which account sends the email. The snippet_id selects the email template to use. Use this tool to: - Send an exposé to an interested contact - Send a ...
Part of the Propstack server.
Free to start. No card required.
AI agents use send_email 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 send_email 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": {
"send_email": {
"limits": [
{
"counter": "send_email_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 send_email 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.
Send an email using a Propstack email template (snippet). Propstack sends emails through connected broker email accounts. The broker_id determines which account sends the email. The snippet_id selects the email template to use. Use this tool to: - Send an exposé to an interested contact - Send a follow-up email after a viewing - Send a confirmation or rejection to a lead Link the email to contacts, properties, and projects so it appears in the correct CRM activity feeds. Important: - broker_id must be a broker with a connected email account - snippet_id is the email template ID — the template may contain merge fields that Propstack fills automatically (contact name, property details, etc.) - to[] are the recipient email addresses - cc[] are optional CC recipients. 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 send_email: 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.
send_email 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 send_email 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 send_email. 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.
send_email 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.