특정 컨트롤러의 모든 path를 가져옵니다
AI agents call get_paths_by_controller to retrieve information from Swagger Parser without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | |
controller | string | Yes |
Parameters from the server's own tool schema.
This tool queries and returns metadata about API paths associated with a controller from an already-loaded Swagger/OpenAPI specification. It performs data retrieval only, consistent with sibling tools like get_controllers and get_path_details. No data is created, modified, deleted, or executed—only extracted from the parsed specification.
From the tool's definition Tool name 'get_paths_by_controller' and description indicate retrieval of paths from a specific controller.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
특정 컨트롤러의 모든 path를 가져옵니다. It is categorised as a Read tool in the Swagger Parser MCP Server, which means it retrieves data without modifying state.
get_paths_by_controller accepts 2 parameters: url, controller. Required: url, controller. The full parameter table on this page comes from the server's own tool schema.
Register the Swagger Parser MCP server in PolicyLayer and add a rule for get_paths_by_controller: 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 Swagger Parser. Nothing to install.
get_paths_by_controller 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 get_paths_by_controller 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 get_paths_by_controller. 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.
get_paths_by_controller is provided by the Swagger Parser MCP server (swagger-parser-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →