📊 Get status of running project servers. USE WHEN: You need to check if a server is running or find its endpoint WHAT THIS DOES: - If project_id provided: checks status of that specific project
AI agents call indexfoundry_project_serve_status to retrieve information from IndexFoundry MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about existing project servers without making any changes, executing commands, or triggering side effects. It is a simple monitoring/inspection operation that falls squarely into the Read category. The low severity reflects minimal blast radius—an AI agent misusing this would only gain visibility into what servers are running, not cause operational harm or data loss.
From the tool's definition Tool description explicitly states 'Get status of running project servers' and use case is 'check if a server is running or find its endpoint'. These are pure read operations with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
📊 Get status of running project servers. USE WHEN: You need to check if a server is running or find its endpoint WHAT THIS DOES: - If project_id provided: checks status of that specific project. It is categorised as a Read tool in the IndexFoundry MCP MCP Server, which means it retrieves data without modifying state.
Register the IndexFoundry MCP server in PolicyLayer and add a rule for indexfoundry_project_serve_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 IndexFoundry MCP. Nothing to install.
indexfoundry_project_serve_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 indexfoundry_project_serve_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 indexfoundry_project_serve_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.
indexfoundry_project_serve_status is provided by the IndexFoundry MCP server (mnehmos/mnehmos.index-foundry.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 →