Send a message to the Agentforce agent and get the response.
AI agents invoke send_message_to_agent to trigger actions in Agentforce MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool sends messages to an AI agent and retrieves responses, triggering external operations within Salesforce Agentforce. The actual effects depend on the message content — an agent could take arbitrary actions (create records, update data, trigger workflows, etc.) in Salesforce based on the message sent.
From the tool's definition Send a message to the Agentforce agent and get the response
Documented attack patterns abuse exactly the kind of access send_message_to_agent gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentforce MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send_message_to_agent:
{
"version": "1",
"default": "deny",
"tools": {
"send_message_to_agent": {
"limits": [
{
"counter": "send_message_to_agent_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} send_message_to_agent stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Send a message to the Agentforce agent and get the response. It is categorised as a Execute tool in the Agentforce MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Agentforce MCP Server MCP server in PolicyLayer and add a rule for send_message_to_agent: 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 Agentforce MCP Server. Nothing to install.
send_message_to_agent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_message_to_agent 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_message_to_agent. 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_message_to_agent is provided by the Agentforce MCP Server MCP server (xlengelle-sf/agentforce-mcp-xlengelle). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agentforce MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Agentforce MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.