sf_update_dashboard
Updates an existing Dashboard
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-update-dashboard.md
What sf_update_dashboard does on Salesforce Metadata Mcp
AI agents use sf_update_dashboard to create or update resources in Salesforce Metadata Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce Metadata Mcp environment.
Why sf_update_dashboard is rated Medium
This tool modifies dashboard metadata in Salesforce, which is a create/update operation (Write category). Dashboards control business intelligence visibility and metrics; misconfiguration could mislead decision-making or expose sensitive data to unintended users. However, the change is reversible and does not permanently delete data or move money, so severity is medium rather than high or critical.
From the tool's definition Tool name is 'sf_update_dashboard' and description states 'Updates an existing Dashboard', indicating modification of data in a reversible manner.
Attacks that exploit this kind of access
The rule that runs sf_update_dashboard safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Salesforce Metadata Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sf_update_dashboard, this is the rule to start with:
sf_update_dashboard 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 Salesforce Metadata Mcp, apply this rule, and every sf_update_dashboard call is checked against it from then on.
Questions about sf_update_dashboard
Updates an existing Dashboard. It is categorised as a Write tool in the Salesforce Metadata Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_update_dashboard: 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 Salesforce Metadata Mcp. Nothing to install.
sf_update_dashboard 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 sf_update_dashboard 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 sf_update_dashboard. 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.
sf_update_dashboard is provided by the Salesforce Metadata MCP server (salesforce-metadata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Salesforce Metadata, and thousands of servers like it.
This server
Across the catalogue