jq
Processes and transforms JSON using jq expressions. Accepts JSON from a file path or inline string. Returns the transformed result.
This record as markdown: /tools/io-github-dave-london-pare-test/jq.md
What jq does on Test
AI agents invoke jq 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.
Why jq is rated High
The tool executes arbitrary jq expressions against JSON data. While jq is primarily a query/transform language, it can execute complex expressions and filters with side effects depending on the environment. The ability to run arbitrary expressions classifies this as Execute rather than Read, since the behavior is entirely argument-dependent.
From the tool's definition Processes and transforms JSON using jq expressions
Attacks that exploit this kind of access
The rule that runs jq safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Test, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jq, this is the rule to start with:
jq 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Test, apply this rule, and every jq call is checked against it from then on.
Questions about jq
Processes and transforms JSON using jq expressions. Accepts JSON from a file path or inline string. Returns the transformed result. 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 jq: 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.
jq 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 jq 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 jq. 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.
jq 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.
More on Test, and thousands of servers like it.
This server
Across the catalogue