Get an index of all entries (slugs and titles only). This is faster than relentless_list when you only need to see what entries exist without their full content. Useful for navigation or sitemap generation.
AI agents call relentless_index to retrieve information from Relentless MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
relentless_index retrieves metadata (slugs and titles) from Notion databases for navigation or discovery purposes. It performs no modifications, deletions, or external operations—purely a read query. The low severity reflects minimal risk even if misused, as it only exposes existing entry identifiers and names without enabling data modification or financial impact.
From the tool's definition Tool description states it 'Get an index of all entries (slugs and titles only)' and is 'faster than relentless_list when you only need to see what entries exist without their full content.' This is a retrieval operation with no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get an index of all entries (slugs and titles only). This is faster than relentless_list when you only need to see what entries exist without their full content. Useful for navigation or sitemap generation. It is categorised as a Read tool in the Relentless MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Relentless MCP Server MCP server in PolicyLayer and add a rule for relentless_index: 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 Relentless MCP Server. Nothing to install.
relentless_index 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 relentless_index 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 relentless_index. 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.
relentless_index is provided by the Relentless MCP Server MCP server (pranaythesingh/relentless-mcp). 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 →