Low Risk

read_messages

Read messages from person or conversation. Args: from_phone (number or group ID), instance_name, limit, before_message_id (for pagination). Returns: messages newest first, with pagination info.

How to control read_messages ↓

What read_messages does on Automagik Tools

AI agents call read_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.

Low Risk

Why read_messages needs a policy

This tool retrieves or queries message data without any side effects. It performs a read-only operation that returns existing messages with pagination support. The parameters (from_phone, instance_name, limit, before_message_id) are all for filtering and retrieving data. There is no capability to modify, delete, execute commands, or process financial transactions.

From the tool's definition Tool name is 'read_messages' and description states 'Read messages from person or conversation' with parameters for querying and pagination. No modification, deletion, or execution of external operations is described.

Documented attack patterns abuse exactly the kind of access read_messages gives an agent:

How to control read_messages

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 read_messages:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_messages": {}
  }
}

read_messages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Automagik Tools — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about read_messages

What does the read_messages tool do? +

Read messages from person or conversation. Args: from_phone (number or group ID), instance_name, limit, before_message_id (for pagination). Returns: messages newest first, with pagination info. It is categorised as a Read tool in the Automagik Tools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_messages? +

Register the Automagik Tools MCP server in PolicyLayer and add a rule for read_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.

What risk level is read_messages? +

read_messages is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit read_messages? +

Yes. Add a rate_limit block to the read_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.

How do I block read_messages completely? +

Set action: deny in the PolicyLayer policy for read_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.

What MCP server provides read_messages? +

read_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.

Enforce policy on every Automagik Tools tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.