Read slide content from a Marp file. Returns a specific slide by ID, or all slides with their IDs and positions.
AI agents call read_slide to retrieve information from Marp MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and queries existing slide data from Marp presentation files. It performs no creation, modification, deletion, or execution of external operations. The operation is read-only with no side effects, fitting squarely into the Read category with minimal risk.
From the tool's definition Tool name 'read_slide' and description states it 'Read slide content from a Marp file. Returns a specific slide by ID, or all slides' — explicitly a retrieval operation with no modifications.
Documented attack patterns abuse exactly the kind of access read_slide gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Marp MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for read_slide:
{
"version": "1",
"default": "deny",
"tools": {
"read_slide": {}
}
} read_slide 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.
Read slide content from a Marp file. Returns a specific slide by ID, or all slides with their IDs and positions. It is categorised as a Read tool in the Marp MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Marp MCP Server MCP server in PolicyLayer and add a rule for read_slide: 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 Marp MCP Server. Nothing to install.
read_slide 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 read_slide 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 read_slide. 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.
read_slide is provided by the Marp MCP Server MCP server (masaki39/marp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Marp 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.
11 Marp MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.