update_settings

Update or retrieve an agent's settings. Requires api_key for updates. Use action='get' to retrieve (no api_key needed).

SERVERAi Agent Bank SOURCEhttps://tdueqhfxyojmjgactdyc.supabase.co/functions/v1/mcp-server

Medium RISK CLASS

Category Write

Parameters 111 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-wirternow-agent-bank/update-settings.md

WHAT IT DOES

What update_settings does on Ai Agent Bank

AI agents use update_settings to create or update resources in Ai Agent Bank, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ai Agent Bank environment.

Parameter	Type	Required	Description
`action`	string	—	'update' (default) or 'get'
`api_key`	string	—	Your api_key (required for updates)
`agent_id`	string	Yes	UUID of the agent
`settings`	object	—	Nested settings object (alternative to flat params)
`auto_yield`	boolean	—	Enable automatic yield optimization
`max_daily_spend`	number	—	Maximum daily spend limit in USDC (alias: daily_spend_limit)
`max_spend_per_tx`	number	—	Alias for max_single_transaction_spend
`preferred_tokens`	array	—	Preferred token symbols
`daily_spend_limit`	number	—	Alias for max_daily_spend
`notification_webhook`	string	—	Webhook URL for notifications
`max_single_transaction_spend`	number	—	Maximum single transaction limit in USDC (alias: max_spend_per_tx)

Parameters from the server's own tool schema.

RISK

Why update_settings is rated Medium

The tool modifies agent settings reversibly (Write category) rather than irreversibly deleting them (Destructive) or executing code (Execute). While the server handles financial operations, this specific tool updates configuration rather than moving funds directly (Financial).

From the tool's definition Tool description states "Update or retrieve an agent's settings" with requirement of api_key for updates. The verb 'update' indicates data modification. Context of financial infrastructure (wallets, USDC transfers) increases severity of configuration changes.

Risk signalsHandles credentials or secrets (api_key) · High parameter count (18 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_settings safely

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

update_settings Rate-limited

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.

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about update_settings

What does the update_settings tool do? +

Update or retrieve an agent's settings. Requires api_key for updates. Use action='get' to retrieve (no api_key needed). It is categorised as a Write tool in the Ai Agent Bank MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_settings accept? +

update_settings accepts 11 parameters: action, api_key, agent_id, settings, auto_yield, max_daily_spend, max_spend_per_tx, preferred_tokens, daily_spend_limit, notification_webhook, max_single_transaction_spend. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_settings? +

Register the Ai Agent Bank 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 Ai Agent Bank. 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 Ai Agent Bank MCP server (https://tdueqhfxyojmjgactdyc.supabase.co/functions/v1/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ai Agent Bank, and thousands of servers like it.

This server

All 43 Ai Agent Bank tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →