Low Risk

messages_get

Get details of a specific message

How to control messages_get ↓

What messages_get does on Propresenter

AI agents call messages_get to retrieve information from Propresenter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why messages_get needs a policy

This tool retrieves or queries message details with no side effects. It performs a read-only operation typical of data lookup functions. The low severity reflects minimal risk if misused by an AI agent, as retrieving message details cannot cause damage or unintended state changes.

From the tool's definition Tool name 'messages_get' and description 'Get details of a specific message' indicate data retrieval without modification. The verb 'Get' and the context within a presentation software (ProPresenter 7) suggest querying existing message data.

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

How to control messages_get

PolicyLayer is an MCP gateway — it sits between your AI agents and Propresenter, and nothing reaches the server without passing your rules. This is the rule we recommend for messages_get:

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

messages_get 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 Propresenter — 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 messages_get

What does the messages_get tool do? +

Get details of a specific message. It is categorised as a Read tool in the Propresenter MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on messages_get? +

Register the Propresenter MCP server in PolicyLayer and add a rule for messages_get: 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 Propresenter. Nothing to install.

What risk level is messages_get? +

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

Can I rate-limit messages_get? +

Yes. Add a rate_limit block to the messages_get 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 messages_get completely? +

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

messages_get is provided by the Propresenter MCP server (@alxpark/propresenter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Propresenter tool call.

Start from Propresenter, 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.

177 Propresenter 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.