gateway_get_profile
Retrieve the active routing profile to view session permissions and restrictions for accessing aggregated MCP servers through a single gateway.
Instructions
Show the active routing profile for this session and what it allows or denies.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Implementation Reference
- benchmarks/token_savings.py:88-145 (schema)The MCP gateway tools are defined here. Note that 'gateway_get_profile' is NOT in this list, which contains the standard meta-MCP gateway tools ('gateway_list_servers', 'gateway_search_tools', 'gateway_invoke'). Based on the codebase analysis, it appears the tool 'gateway_get_profile' does not exist in the provided repository.
GATEWAY_TOOLS = [ { "name": "gateway_list_servers", "description": ( "List all registered MCP backend servers with their names, " "descriptions, and tool counts. Use this first to discover " "available capabilities." ), "inputSchema": { "type": "object", "properties": {}, }, }, { "name": "gateway_search_tools", "description": ( "Search for tools across all registered backends by keyword. " "Returns matching tool names, descriptions, and which backend " "they belong to. Use this to find the right tool before invoking." ), "inputSchema": { "type": "object", "properties": { "query": { "type": "string", "description": "Search query to match against tool names and descriptions.", }, }, "required": ["query"], }, }, { "name": "gateway_invoke", "description": ( "Invoke a specific tool on a specific backend server. " "Pass the server name, tool name, and arguments. " "The gateway routes the request and returns the result." ), "inputSchema": { "type": "object", "properties": { "server": { "type": "string", "description": "Name of the backend MCP server.", }, "tool": { "type": "string", "description": "Name of the tool to invoke.", }, "arguments": { "type": "object", "description": "Arguments to pass to the tool.", }, }, "required": ["server", "tool"], }, }, ]