capture_get_settings

Get the current capture settings

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/capture-get-settings.md

WHAT IT DOES

What capture_get_settings does on Propresenter

AI agents call capture_get_settings 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.

RISK

Why capture_get_settings is rated Low

This tool retrieves capture settings from ProPresenter 7 without making any changes. It performs a read-only query operation with no side effects, placing it in the Read category. The severity is low as exposure of capture settings configuration poses minimal risk to system integrity or security.

From the tool's definition Tool name includes 'get_' prefix and description states 'Get the current capture settings', indicating a query operation that retrieves configuration without modifying state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs capture_get_settings safely

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

capture_get_settings Allowed

capture_get_settings 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": {
    "capture_get_settings": {}
  }
}

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

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

FAQ

Questions about capture_get_settings

What does the capture_get_settings tool do? +

Get the current capture settings. 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 capture_get_settings? +

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

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

Can I rate-limit capture_get_settings? +

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

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

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

KEEP EXPLORING

More on Propresenter, and thousands of servers like it.

This server

All 177 Propresenter tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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