AI agents invoke info to trigger actions in Test. 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.
Given the server context (running tests) and the truncated description 'Runs', this tool likely executes some kind of runtime command or test framework introspection. Sibling tools like ansible-playbook, bazel, and apply further suggest an execution-oriented environment. Since the description is incomplete, confidence is low, but Execute is the best fit given context.
From the tool's definition Tool is named 'info' on a server described as auto-detecting and running test frameworks (pytest, jest, vitest, mocha). The description only says 'Runs' with no further detail.
Documented attack patterns abuse exactly the kind of access info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Test, and nothing reaches the server without passing your rules. This is the rule we recommend for info:
{
"version": "1",
"default": "deny",
"tools": {
"info": {
"limits": [
{
"counter": "info_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}info stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Runs. It is categorised as a Execute tool in the Test MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Test MCP server in PolicyLayer and add a rule for info: 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 Test. Nothing to install.
info 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 info 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 info. 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.
info is provided by the Test MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Test, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Test tools catalogued and risk-classified — across an index of 43,000+ MCP servers.