Check if Expo development server is running and get app status
AI agents call check_expo_dev_server to retrieve information from Enhanced Web Scraper MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a diagnostic check to verify server status and retrieve app status—purely informational queries with no side effects. It does not execute arbitrary commands, modify data, delete resources, or trigger operations. The action is passive monitoring/reporting, which falls squarely under Read category.
From the tool's definition Tool name 'check_expo_dev_server' and description 'Check if Expo development server is running and get app status' indicate query/diagnostic operations that retrieve status information without modifying state, executing code, or affecting systems.
Attacks that exploit this kind of access
Check if Expo development server is running and get app status. It is categorised as a Read tool in the Enhanced Web Scraper MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced Web Scraper MCP Server MCP server in PolicyLayer and add a rule for check_expo_dev_server: 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 Enhanced Web Scraper MCP Server. Nothing to install.
check_expo_dev_server 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 check_expo_dev_server 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 check_expo_dev_server. 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.
check_expo_dev_server is provided by the Enhanced Web Scraper MCP Server MCP server (jmrmedev/amazon-q-web-scraper-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 →