update_source_settings · CustomGPT MCP Server MCP

WHAT IT DOES

What update_source_settings does on CustomGPT MCP Server

AI agents use update_source_settings to create or update resources in CustomGPT MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CustomGPT MCP Server environment.

WHY IT NEEDS A POLICY

Why update_source_settings needs a policy

The tool modifies source settings (sitemap or upload configuration) but does not delete or irreversibly destroy data. Updates are typically reversible—settings can be changed again. This falls clearly into Write category. Severity is medium because misconfigured source settings could affect data availability or agent behavior, but the impact is localized to a single source and can be corrected.

From the tool's definition Tool name contains 'update' and description states 'Update settings for a specific source', indicating modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_source_settings Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CustomGPT MCP Server, so you can run agents against it safely.

FAQ

Questions about update_source_settings

What does the update_source_settings tool do? +

Update settings for a specific source (sitemap or upload). It is categorised as a Write tool in the CustomGPT MCP Server 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_source_settings? +

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

What risk level is update_source_settings? +

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

Can I rate-limit update_source_settings? +

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

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

update_source_settings is provided by the CustomGPT MCP Server MCP server (poll-the-people/customgpt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.