upsert_guardrail_mcp_server
Create or replace a guardrail-to-MCP-server mapping while preserving mappings for other servers; optionally set input/output run phases, defaulting to both.
Instructions
Create or replace one guardrail mapping for one MCP server without changing mappings for other servers. Requires a guardrail with target mcp_tools. run_on defaults to both input and output. Use list_guardrail_mcp_servers to inspect the current mapping set first. Repeating the same mapping is safe.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"guardrail_id": "<guardrail_id>",
"mcp_server_id": "<mcp_server_id>"
},
"name": "upsert_guardrail_mcp_server"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| run_on | No | Guardrail phases to run for this MCP server | |
| guardrail_id | Yes | Guardrail UUID or slug | |
| mcp_server_id | Yes | MCP server UUID | |
| mcp_integration_capability_ids | No | MCP integration capability UUIDs covered by this mapping |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | Call succeeded | |
| data | No | Success payload | |
| error | No | Failure details |