Check recent incoming messages. Args: instance_name, hours (lookback), limit. Returns: messages grouped by sender.
AI agents call check_new_messages to retrieve information from Automagik Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries message data without side effects. It reads recent messages within a specified lookback window and limit, returning them in a structured format. No data is created, modified, or deleted. This is a straightforward Read operation with low blast radius even if an AI agent calls it unexpectedly.
From the tool's definition Tool description states 'Check recent incoming messages' and 'Returns: messages grouped by sender' — pure data retrieval with no modification, creation, or deletion of messages.
Documented attack patterns abuse exactly the kind of access check_new_messages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Automagik Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for check_new_messages:
{
"version": "1",
"default": "deny",
"tools": {
"check_new_messages": {}
}
}check_new_messages 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.
Check recent incoming messages. Args: instance_name, hours (lookback), limit. Returns: messages grouped by sender. It is categorised as a Read tool in the Automagik Tools MCP Server, which means it retrieves data without modifying state.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for check_new_messages: 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 Automagik Tools. Nothing to install.
check_new_messages 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 check_new_messages 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 check_new_messages. 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.
check_new_messages is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Automagik Tools, 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.
122 Automagik Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.