update_settings

THE RISK

Medium Risk

Why update_settings needs a policy

This tool creates or modifies application configuration data in the Web UI. Updates to settings are write operations that can be reverted by changing them again, making this Write rather than Destructive. While it affects how content is rendered, it does not execute arbitrary code, delete data, or move funds.

From the tool's definition Tool description explicitly states 'Update rendering settings' and enumerates modifiable parameters (caption style, crop strategy, logo, outro), which are configuration changes that persist but are reversible.

Documented attack patterns abuse exactly the kind of access update_settings gives an agent:

POLICY

How to control update_settings

PolicyLayer is an MCP gateway — it sits between your AI agents and Podcli, and nothing reaches the server without passing your rules. This is the rule we recommend for update_settings:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_settings": {
      "limits": [
        {
          "counter": "update_settings_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_settings stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Podcli — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Podcli tools

Execute parse_transcript Parse a raw speaker-labeled plain text transcript into word-level timestamps. Input format Execute batch_create_clips STEP 3 — Export multiple clips at once as finished vertical shorts.\n\n Execute transcribe_podcast STEP 1 — Transcribe a podcast video/audio file. This is typically the first tool you call. Write create_clip STEP 3 — Export a single clip as a finished vertical short (1080x1920, 9:16).\n\n Write import_transcript Import an external transcript (e.g. from a transcription service) into the UI. Skips Whisp Write knowledge_base Read or manage the podcli knowledge base. These are .md files that provide context about t Write manage_assets Register and manage reusable assets (logos, videos). Registered assets can be referenced b Write manage_presets Save, load, list, or delete rendering presets. Presets store caption_style, crop_strategy,

All 17 Podcli tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_settings

What does the update_settings tool do? +

Update rendering settings (caption style, crop strategy, logo, outro) in the Web UI. It is categorised as a Write tool in the Podcli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_settings? +

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

What risk level is update_settings? +

update_settings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_settings? +

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

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

update_settings is provided by the Podcli MCP server (nmbrthirteen/podcli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Podcli tool call.

Start from Podcli, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →