Test Management - Write test code, run tests, and report results.
AI agents invoke test to trigger actions in Node Js MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool explicitly runs test code, which constitutes execution of code whose effects depend on what tests are written. Writing test code ('Write test code') also involves creating/modifying files. The most severe applicable category is Execute due to the 'run tests' capability. Misuse could involve running malicious code disguised as tests, giving it a high severity rating.
From the tool's definition 'run tests' — the tool executes test code and reports results, implying arbitrary code execution in a runtime environment
Attacks that exploit this kind of access
Test Management - Write test code, run tests, and report results. It is categorised as a Execute tool in the Node Js MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Node Js MCP Server MCP server in PolicyLayer and add a rule for 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 Node Js MCP Server. Nothing to install.
test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the 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 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.
test is provided by the Node Js MCP Server MCP server (mustafa-can/mcpserver). 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 →