AI agents call get_message_seen_status to retrieve information from Frontapp MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about whether a message has been seen, which is a read-only query operation. It does not create, modify, delete, or execute any actions. The verb 'Get' combined with the fact it returns status information (not performing any action) clearly places this in the Read category. Blast radius is minimal since viewing message status information poses no security risk.
From the tool's definition Tool name contains 'get_message_seen_status' and description states 'Get the seen status of a message' — both indicate a retrieval operation with no data modification or side effects.
Documented attack patterns abuse exactly the kind of access get_message_seen_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Frontapp MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_message_seen_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_message_seen_status": {}
}
}get_message_seen_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the seen status of a message. It is categorised as a Read tool in the Frontapp MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Frontapp MCP Server MCP server in PolicyLayer and add a rule for get_message_seen_status: 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 Frontapp MCP Server. Nothing to install.
get_message_seen_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_message_seen_status 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 get_message_seen_status. 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.
get_message_seen_status is provided by the Frontapp MCP Server MCP server (zqushair/frontapp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Frontapp 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.
151 Frontapp MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.