playlists_get_focused_next

Get the next item in the focused playlist

SERVERPropresenter SOURCE@alxpark/propresenter-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alxpark-propresenter-mcp/playlists-get-focused-next.md

What playlists_get_focused_next does on Propresenter

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

Why playlists_get_focused_next is rated Low

This tool queries the state of a playlist (retrieving the next item) without modifying, executing, or deleting any data. It is a simple read operation consistent with the Read category. The blast radius of misuse is minimal—incorrect reads cannot harm the presentation system or data. Severity is low because there are no side effects from this information retrieval.

From the tool's definition Tool name 'playlists_get_focused_next' and description 'Get the next item in the focused playlist' indicate a retrieval operation with no side effects.

Questions about playlists_get_focused_next

What does the playlists_get_focused_next tool do? +

Get the next item in the focused playlist. 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 playlists_get_focused_next? +

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

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

Can I rate-limit playlists_get_focused_next? +

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

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

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

More on Propresenter, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Propresenter's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.