ppt_read

Reads slide text content from a PowerPoint (.pptx) file.

SERVERLocal SOURCElocal-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/ppt-read.md

WHAT IT DOES

What ppt_read does on Local

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

Parameter	Type	Required	Description
`path`	string	Yes	Absolute path to the .pptx file

Parameters from the server's own tool schema.

RISK

Why ppt_read is rated Low

This tool performs data retrieval (reading slide text) with no capability to modify, delete, execute code, or cause irreversible changes. It is a straightforward Read operation with minimal risk even if misused by an AI agent, as the worst case is unauthorized access to text content already stored locally on the user's Mac.

From the tool's definition Tool name 'ppt_read' and description 'Reads slide text content from a PowerPoint (.pptx) file' clearly indicate a read-only operation that retrieves data without modification or side effects.

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ppt_read safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ppt_read, this is the rule to start with:

ppt_read Allowed

ppt_read is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every ppt_read call is checked against it from then on.

FAQ

Questions about ppt_read

What does the ppt_read tool do? +

Reads slide text content from a PowerPoint (.pptx) file. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.

What parameters does ppt_read accept? +

ppt_read accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ppt_read? +

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

What risk level is ppt_read? +

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

Can I rate-limit ppt_read? +

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

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

ppt_read is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →