swagger_list_endpoints_by_tag

List all endpoints belonging to a specific tag

Server Multi-Database MCP Server nam088/mcp-server
Category Read
Risk class Low
Parameters 00 required

What swagger_list_endpoints_by_tag does on Multi-Database MCP Server

AI agents call swagger_list_endpoints_by_tag to retrieve information from Multi-Database MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why swagger_list_endpoints_by_tag needs a policy

This tool retrieves and displays endpoint information from API documentation metadata. It has no side effects on data or systems—it only queries and returns existing information about API structure. This is a classic Read category operation with minimal security risk. The context of a multi-database MCP server does not change the nature of this specific tool, which operates on Swagger metadata, not database state.

From the tool's definition Tool name 'swagger_list_endpoints_by_tag' and description 'List all endpoints belonging to a specific tag' indicate a retrieval operation that queries Swagger/OpenAPI metadata. The verb 'list' is a non-mutating read operation.

Questions about swagger_list_endpoints_by_tag

What does the swagger_list_endpoints_by_tag tool do? +

List all endpoints belonging to a specific tag. It is categorised as a Read tool in the Multi-Database MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on swagger_list_endpoints_by_tag? +

Register the Multi-Database MCP Server MCP server in PolicyLayer and add a rule for swagger_list_endpoints_by_tag: 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 Multi-Database MCP Server. Nothing to install.

What risk level is swagger_list_endpoints_by_tag? +

swagger_list_endpoints_by_tag is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit swagger_list_endpoints_by_tag? +

Yes. Add a rate_limit block to the swagger_list_endpoints_by_tag 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.

How do I block swagger_list_endpoints_by_tag completely? +

Set action: deny in the PolicyLayer policy for swagger_list_endpoints_by_tag. 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.

What MCP server provides swagger_list_endpoints_by_tag? +

swagger_list_endpoints_by_tag is provided by the Multi-Database MCP Server MCP server (nam088/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.