list_input_guardrail_workspace_exclusions
List workspaces excluded from organisation-wide input guardrails for one organisation. Use this to audit exceptions or establish the current state before the matching update tool; it reads input exclusions only and does not return the organisation
This record as markdown: /tools/codeswhat-portkey-admin-mcp/list-input-guardrail-workspace-exclusions.md
What list_input_guardrail_workspace_exclusions does on Portkey Admin
AI agents call list_input_guardrail_workspace_exclusions to retrieve information from Portkey Admin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_input_guardrail_workspace_exclusions is rated Low
Tool retrieves guardrail exclusion data without modifying state or triggering external operations.
From the tool's definition List workspaces excluded, reads input exclusions only, does not return organisation
Attacks that exploit this kind of access
The rule that runs list_input_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 list_input_guardrail_workspace_exclusions, this is the rule to start with:
list_input_guardrail_workspace_exclusions is read-only, so it stays allowed. 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 list_input_guardrail_workspace_exclusions call is checked against it from then on.
Questions about list_input_guardrail_workspace_exclusions
List workspaces excluded from organisation-wide input guardrails for one organisation. Use this to audit exceptions or establish the current state before the matching update tool; it reads input exclusions only and does not return the organisation. It is categorised as a Read tool in the Portkey Admin MCP Server, which means it retrieves data without modifying state.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for list_input_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.
list_input_guardrail_workspace_exclusions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_input_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 list_input_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.
list_input_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