windsurf_set_usage_config
Update Windsurf/Codeium usage configuration settings for the team
This record as markdown: /tools/sagemcp-sagemcp/windsurf-set-usage-config.md
What windsurf_set_usage_config does on Sage MCP
AI agents use windsurf_set_usage_config to create or update resources in Sage MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sage MCP environment.
Why windsurf_set_usage_config is rated Medium
This tool creates or modifies configuration data (usage settings) for a team, which is a reversible change. It does not execute arbitrary code, delete data permanently, move money, or trigger external operations. The 'team' scope and configuration nature suggests a moderate blast radius if misconfigured by an AI agent (could affect team productivity or security policies), warranting medium severity.
From the tool's definition Tool name 'windsurf_set_usage_config' contains 'set', indicating a configuration update operation. Description states 'Update Windsurf/Codeium usage configuration settings for the team', confirming it modifies settings reversibly.
Attacks that exploit this kind of access
The rule that runs windsurf_set_usage_config safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For windsurf_set_usage_config, this is the rule to start with:
windsurf_set_usage_config 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every windsurf_set_usage_config call is checked against it from then on.
Questions about windsurf_set_usage_config
Update Windsurf/Codeium usage configuration settings for the team. It is categorised as a Write tool in the Sage MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sage MCP server in PolicyLayer and add a rule for windsurf_set_usage_config: 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 Sage MCP. Nothing to install.
windsurf_set_usage_config 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 windsurf_set_usage_config 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 windsurf_set_usage_config. 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.
windsurf_set_usage_config is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sage, and thousands of servers like it.
This server
Across the catalogue