Mark a message as seen in a direct message thread. Args: thread_id: The thread ID containing the message. message_id: The ID of the message to mark as seen. Returns: A dictionary with success status and a status message.
AI agents use mark_message_seen 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 performs a state modification (marking seen status) on existing data rather than creating new data, retrieving data, executing external operations, or destroying data. It is clearly Write category. Severity is low because marking messages as seen has minimal blast radius—it is a benign, user-facing interaction pattern with no financial, destructive, or security implications.
From the tool's definition Tool modifies message state by marking it as 'seen' in Instagram's direct message system. Description states it marks a message as seen, which is a reversible state change to an existing data object (the message).
Documented attack patterns abuse exactly the kind of access mark_message_seen 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 mark_message_seen:
{
"version": "1",
"default": "deny",
"tools": {
"mark_message_seen": {
"limits": [
{
"counter": "mark_message_seen_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mark_message_seen 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.
Mark a message as seen in a direct message thread. Args: thread_id: The thread ID containing the message. message_id: The ID of the message to mark as seen. Returns: A dictionary with success status and a status message. 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 mark_message_seen: 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.
mark_message_seen 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 mark_message_seen 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 mark_message_seen. 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.
mark_message_seen is provided by the Instagram DM MCP Server MCP server (trypeggy/instagram_dm_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Instagram DM MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
25 Instagram DM MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.