macros_get

THE RISK

Low Risk

Why macros_get needs a policy

This tool retrieves or queries macro details from ProPresenter 7 without creating, modifying, or deleting any data. It is a straightforward read operation on presentation metadata, typical of query/fetch operations with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'macros_get' and description 'Get details of a specific macro' indicate a retrieval operation with no side effects.

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

POLICY

How to control macros_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 macros_get:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "macros_get": {}
  }
}

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

Create a free account and register Propresenter — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Propresenter tools

Destructive clear_layer Clear a specific layer (audio, props, messages, announcements, slide, media, video_input) Destructive messages_delete Delete a specific message Destructive props_clear Clear a specific prop from display Destructive props_delete Delete a specific prop Destructive props_delete_collection Delete a specific prop collection Destructive stage_delete_layout Delete a specific stage layout Execute clear_trigger_group Trigger a specific clear group Execute props_pause_auto_clear Pause auto-clear for a specific prop

All 177 Propresenter tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about macros_get

What does the macros_get tool do? +

Get details of a specific macro. 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 macros_get? +

Register the Propresenter MCP server in PolicyLayer and add a rule for macros_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 macros_get? +

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

Can I rate-limit macros_get? +

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

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

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

CHECK YOUR STACK →