gluecron_generate_tests
Generate tests for a PR via Claude. Wraps src/lib/ai-test-generator.generateTestsForPr. Mode 'follow-up-pr' opens a new PR; 'append-commit' commits onto the head branch. Requires 'repo' scope.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-generate-tests.md
What gluecron_generate_tests does on Gluecron
AI agents invoke gluecron_generate_tests to trigger actions in Gluecron. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | — | 'follow-up-pr' or 'append-commit' |
repo | string | Yes | |
owner | string | Yes | |
number | number | Yes | PR number |
Parameters from the server's own tool schema.
Why gluecron_generate_tests is rated High
Tool triggers AI code generation and commits or opens PRs, executing external write operations.
From the tool's definition commits onto the head branch, opens a new PR
Attacks that exploit this kind of access
The rule that runs gluecron_generate_tests safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gluecron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gluecron_generate_tests, this is the rule to start with:
gluecron_generate_tests 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 Gluecron, apply this rule, and every gluecron_generate_tests call is checked against it from then on.
Questions about gluecron_generate_tests
Generate tests for a PR via Claude. Wraps src/lib/ai-test-generator.generateTestsForPr. Mode 'follow-up-pr' opens a new PR; 'append-commit' commits onto the head branch. Requires 'repo' scope. It is categorised as a Execute tool in the Gluecron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
gluecron_generate_tests accepts 4 parameters: mode, repo, owner, number. Required: repo, owner, number. The full parameter table on this page comes from the server's own tool schema.
Register the Gluecron MCP server in PolicyLayer and add a rule for gluecron_generate_tests: 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 Gluecron. Nothing to install.
gluecron_generate_tests 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 gluecron_generate_tests 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 gluecron_generate_tests. 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.
gluecron_generate_tests is provided by the Gluecron MCP server (https://gluecron.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gluecron, and thousands of servers like it.
Across the catalogue