Update an existing savings goal
AI agents use savings_goal_update to create or update resources in Starling Bank — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Starling Bank environment.
This tool modifies financial account data (a savings goal) reversibly, making it a Write operation. However, given the financial context (modifying savings goals on a banking platform), the severity is elevated to high due to the potential impact on the user's financial planning and account state.
From the tool's definition Tool is named 'savings_goal_update' and described as 'Update an existing savings goal'. The term 'update' indicates modification of existing financial data within the Starling Bank account.
Attacks that exploit this kind of access
Update an existing savings goal. It is categorised as a Write tool in the Starling Bank MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Starling Bank MCP server in PolicyLayer and add a rule for savings_goal_update: 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 Starling Bank. Nothing to install.
savings_goal_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the savings_goal_update 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.
Set action: deny in the PolicyLayer policy for savings_goal_update. 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.
savings_goal_update is provided by the Starling Bank MCP server (starling-bank-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →