This record as markdown: /tools/io-github-dave-london-pare-test/bundle-check.md
What bundle-check does on Test
AI agents call bundle-check to retrieve information from Test without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why bundle-check is rated Low
The tool performs verification of a Gemfile, which is a read-only operation that checks dependencies. No data is created, modified, deleted, or executed. The incomplete description ('Verifies that the Gemfile') limits full certainty, but the name and apparent purpose strongly suggest it only reads and validates configuration state.
From the tool's definition Tool name 'bundle-check' and description 'Verifies that the Gemfile' indicate a validation/checking operation that reads and inspects bundler configuration without modifying or executing code.
Attacks that exploit this kind of access
The rule that runs bundle-check 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 bundle-check, this is the rule to start with:
bundle-check is read-only, so it stays allowed. 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 bundle-check call is checked against it from then on.
Questions about bundle-check
Verifies that the Gemfile. It is categorised as a Read tool in the Test MCP Server, which means it retrieves data without modifying state.
Register the Test MCP server in PolicyLayer and add a rule for bundle-check: 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.
bundle-check 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 bundle-check 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 bundle-check. 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.
bundle-check 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