Low Risk

capture_get_status

Get the current capture status and capture time

Part of the Propresenter MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call capture_get_status to retrieve information from Propresenter without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though capture_get_status only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-alxpark-propresenter-mcp.yaml
tools:
  capture_get_status:
    rules:
      - action: allow

See the full Propresenter policy for all 177 tools.

Tool Name capture_get_status
Category Read
Risk Level Low

View all 177 tools →

What does the capture_get_status tool do? +

Get the current capture status and capture time. 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_status? +

Add a rule in your Intercept YAML policy under the tools section for capture_get_status. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Propresenter MCP server.

What risk level is capture_get_status? +

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

Can I rate-limit capture_get_status? +

Yes. Add a rate_limit block to the capture_get_status rule in your Intercept 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_status completely? +

Set action: deny in the Intercept policy for capture_get_status. 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_status? +

capture_get_status is provided by the Propresenter MCP server (@alxpark/propresenter-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Propresenter

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.