usage_endpoints
Get current user's endpoint usage breakdown. Returns per-endpoint request and credit totals for the selected UTC time range, ordered by request volume.
This record as markdown: /tools/crawlora-mcp/usage-endpoints.md
What usage_endpoints does on Crawlora
AI agents call usage_endpoints to retrieve information from Crawlora without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | — | Custom upper bound in RFC3339 format when range=custom |
from | string | — | Custom lower bound in RFC3339 format when range=custom |
limit | integer | — | Maximum endpoints to return. Defaults to 20 and clamps to 100. |
range | string | — | Time range preset. Defaults to the current billing period. |
Parameters from the server's own tool schema.
Why usage_endpoints is rated Low
Even though usage_endpoints only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs usage_endpoints safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For usage_endpoints, this is the rule to start with:
usage_endpoints is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every usage_endpoints call is checked against it from then on.
Questions about usage_endpoints
Get current user's endpoint usage breakdown. Returns per-endpoint request and credit totals for the selected UTC time range, ordered by request volume. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
usage_endpoints accepts 4 parameters: to, from, limit, range. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for usage_endpoints: 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 Crawlora. Nothing to install.
usage_endpoints 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 usage_endpoints 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 usage_endpoints. 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.
usage_endpoints is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue