AI agents call vectorise_index_status to retrieve information from Vectorise without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name strongly suggests it retrieves status information about indexing operations. This is a read operation that queries state without side effects. Although the description is empty, the naming convention and surrounding tool ecosystem indicate this is a status/monitoring function, not a write, destructive, execute, or financial operation.
From the tool's definition Tool name 'vectorise_index_status' combined with server context showing indexing operations (vectorise_await_index, vectorise_index_project, vectorise_list_jobs, vectorise_list_projects).
Attacks that exploit this kind of access
vectorise_index_status. It is categorised as a Read tool in the Vectorise MCP Server, which means it retrieves data without modifying state.
Register the Vectorise MCP server in PolicyLayer and add a rule for vectorise_index_status: 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 Vectorise. Nothing to install.
vectorise_index_status 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 vectorise_index_status 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 vectorise_index_status. 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.
vectorise_index_status is provided by the Vectorise MCP server (jameslovespancakes/vectorised-embedding-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 →