AI agents use send_dm to create or update resources in Instagram DM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Instagram DM MCP Server environment.
This tool creates new data (Instagram direct messages) in a reversible manner. A message can be deleted by the user, making it Write rather than Destructive. The severity is medium because an AI agent misusing this tool could spam users, impersonate the account holder, or send unwanted/harassing messages at scale, but no financial harm or permanent data loss occurs.
From the tool's definition Tool name 'send_dm' and description 'Send a direct message to an Instagram user' directly indicate the ability to create and post new messages to Instagram accounts.
Documented attack patterns abuse exactly the kind of access send_dm gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Instagram DM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send_dm:
{
"version": "1",
"default": "deny",
"tools": {
"send_dm": {
"limits": [
{
"counter": "send_dm_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send_dm stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Send a direct message to an Instagram user. It is categorised as a Write tool in the Instagram DM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Instagram DM MCP Server MCP server in PolicyLayer and add a rule for send_dm: 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 Instagram DM MCP Server. Nothing to install.
send_dm 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_dm 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_dm. 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_dm is provided by the Instagram DM MCP Server MCP server (taskmaster-ai/insta-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Instagram DM 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.
3 Instagram DM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.