List all endpoints belonging to a specific tag. Use get_spec_info first to see available tags. Supports pagination via limit and offset. Then use get_endpoint to inspect a specific endpoint in detail.
AI agents call list_endpoints_by_tag to retrieve information from Apifable without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists metadata about OpenAPI endpoints filtered by tag. It performs no modifications, deletions, or execution of external operations. The sibling tools (get_endpoint, search_endpoints, search_schemas) confirm the server's role is exploration and introspection of specs rather than mutation or execution. Pagination parameters are read-only query controls.
From the tool's definition Tool description states 'List all endpoints' with 'pagination via limit and offset' — retrieval operations with no side effects. Explicitly recommends using 'get_endpoint' for further inspection, indicating this is a query/browse action.
Documented attack patterns abuse exactly the kind of access list_endpoints_by_tag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apifable, and nothing reaches the server without passing your rules. This is the rule we recommend for list_endpoints_by_tag:
{
"version": "1",
"default": "deny",
"tools": {
"list_endpoints_by_tag": {}
}
}list_endpoints_by_tag is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all endpoints belonging to a specific tag. Use get_spec_info first to see available tags. Supports pagination via limit and offset. Then use get_endpoint to inspect a specific endpoint in detail. It is categorised as a Read tool in the Apifable MCP Server, which means it retrieves data without modifying state.
Register the Apifable MCP server in PolicyLayer and add a rule for 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 Apifable. Nothing to install.
list_endpoints_by_tag 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_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.
Set action: deny in the PolicyLayer policy for 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.
list_endpoints_by_tag is provided by the Apifable MCP server (ycs77/apifable). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apifable, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Apifable tools catalogued and risk-classified — across an index of 43,000+ MCP servers.