long_running_test
AI agents call long_running_test as a supporting operation in MCP Log Analyzer workflows.
The description is empty and the name 'long_running_test' suggests it may be a test/diagnostic utility, but without any description there is insufficient information to assign a meaningful risk category. Given the server context of log analysis, it likely performs some read or execute operation, but this cannot be confirmed. Confidence is very low.
From the tool's definition Tool name is 'long_running_test' with an empty description. No functional information is available.
Attacks that exploit this kind of access
long_running_test. It is categorised as a Other tool in the MCP Log Analyzer MCP Server, which means it performs auxiliary operations.
Register the MCP Log Analyzer MCP server in PolicyLayer and add a rule for long_running_test: 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 MCP Log Analyzer. Nothing to install.
long_running_test is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the long_running_test 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 long_running_test. 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.
long_running_test is provided by the MCP Log Analyzer MCP server (sedwardstx/demomcp). 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 →