Check if the JWT redirect server is running on localhost:8080
AI agents call check_jwt_server_status to retrieve information from EuConquisto Composer MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool merely verifies whether a service is operational by checking its status. No data is retrieved, modified, deleted, or financial operations are involved. This is a simple health check that could be performed by an AI agent safely without risk of unintended side effects beyond discovering the server state.
From the tool's definition Tool performs a status check on a JWT redirect server ('Check if the JWT redirect server is running'). This is a query/diagnostic operation with no data modification or command execution.
Attacks that exploit this kind of access
Check if the JWT redirect server is running on localhost:8080. It is categorised as a Read tool in the EuConquisto Composer MCP MCP Server, which means it retrieves data without modifying state.
Register the EuConquisto Composer MCP server in PolicyLayer and add a rule for check_jwt_server_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 EuConquisto Composer MCP. Nothing to install.
check_jwt_server_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 check_jwt_server_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 check_jwt_server_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.
check_jwt_server_status is provided by the EuConquisto Composer MCP server (rkm097git/euconquisto-composer-mcp-poc). 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 →