update_output_guardrail_workspace_exclusions
Set workspace exclusions from organisation-wide output guardrails. Each entry excludes or restores one workspace; override_existing replaces prior states while the default merge behavior preserves unmentioned workspaces. Review the matching list tool first because enforcement changes immediately....
This record as markdown: /tools/codeswhat-portkey-admin-mcp/update-output-guardrail-workspace-exclusions.md
What update_output_guardrail_workspace_exclusions does on Portkey Admin
AI agents use update_output_guardrail_workspace_exclusions to create or update resources in Portkey Admin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Portkey Admin environment.
Why update_output_guardrail_workspace_exclusions is rated Medium
Modifies guardrail exclusion states with immediate enforcement impact across workspaces; reversible but high-blast configuration change.
From the tool's definition Set workspace exclusions, override_existing replaces, enforcement changes immediately
Attacks that exploit this kind of access
The rule that runs update_output_guardrail_workspace_exclusions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Portkey Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_output_guardrail_workspace_exclusions, this is the rule to start with:
update_output_guardrail_workspace_exclusions 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 Portkey Admin, apply this rule, and every update_output_guardrail_workspace_exclusions call is checked against it from then on.
Questions about update_output_guardrail_workspace_exclusions
Set workspace exclusions from organisation-wide output guardrails. Each entry excludes or restores one workspace; override_existing replaces prior states while the default merge behavior preserves unmentioned workspaces. Review the matching list tool first because enforcement changes immediately. Repeating the same states is safe. Requires an organisation service API key with organisation_exclusions.update scope. It is categorised as a Write tool in the Portkey Admin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for update_output_guardrail_workspace_exclusions: 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 Portkey Admin. Nothing to install.
update_output_guardrail_workspace_exclusions 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 update_output_guardrail_workspace_exclusions 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 update_output_guardrail_workspace_exclusions. 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.
update_output_guardrail_workspace_exclusions is provided by the Portkey Admin MCP server (codeswhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Portkey Admin, and thousands of servers like it.
This server
Across the catalogue