test_guidance

THE RISK

High Risk

Why test_guidance needs a policy

The tool is described as providing guidance for a TEST phase that involves executing tests. While it may primarily return instructional content, it is explicitly tied to test execution workflows. If it triggers or orchestrates test runs, it falls under Execute. The description 'execute tests' suggests actual test invocation rather than purely read-only advice.

From the tool's definition 'execute tests and validate functionality after refactoring' — the tool triggers test execution as part of its mandatory guidance

Documented attack patterns abuse exactly the kind of access test_guidance gives an agent:

POLICY

How to control test_guidance

PolicyLayer is an MCP gateway — it sits between your AI agents and Structured Workflow MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for test_guidance:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_guidance": {
      "limits": [
        {
          "counter": "test_guidance_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

test_guidance 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.

Create a free account and register Structured Workflow MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Structured Workflow MCP tools

Execute build_custom_workflow Build a custom workflow with full control over phases and configuration. Use specific work Execute refactor_workflow Start a structured refactoring workflow to improve existing code without changing function Execute tdd_workflow Start a Test-Driven Development workflow with Red-Green-Refactor cycles Write phase_output Record the output/results when completing a workflow phase - REQUIRES ACTUAL OUTPUT ARTIFA Write test_workflow Start a focused workflow for writing or improving test coverage Write create_feature_workflow Start a structured workflow for adding new functionality with integrated testing Read audit_inventory_guidance Get guidance for the AUDIT_INVENTORY phase - analyze code and catalog changes Read compare_analyze_guidance Get guidance for the COMPARE/ANALYZE phase - evaluating approaches

All 20 Structured Workflow MCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Structured Workflow MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about test_guidance

What does the test_guidance tool do? +

Get MANDATORY guidance for the TEST phase - execute tests and validate functionality after refactoring. It is categorised as a Execute tool in the Structured Workflow MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_guidance? +

Register the Structured Workflow MCP server in PolicyLayer and add a rule for test_guidance: 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 Structured Workflow MCP. Nothing to install.

What risk level is test_guidance? +

test_guidance is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit test_guidance? +

Yes. Add a rate_limit block to the test_guidance 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.

How do I block test_guidance completely? +

Set action: deny in the PolicyLayer policy for test_guidance. 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.

What MCP server provides test_guidance? +

test_guidance is provided by the Structured Workflow MCP server (kingdomseed/structured-workflow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Structured Workflow MCP tool call.

Start from Structured Workflow MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →