testkit_list_specs
List the yaver-test-sdk specs in the current project (yaver-tests//*.test.yaml). Returns name, path, target, step count.
This record as markdown: /tools/io-github-kivanccakmak-yaver/testkit-list-specs.md
What testkit_list_specs does on Yaver
AI agents call testkit_list_specs to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
root | string | — | Spec root directory (default: yaver-tests) |
Parameters from the server's own tool schema.
Why testkit_list_specs is rated Low
The tool performs a read-only operation that enumerates and returns metadata about test specification files. It does not execute tests, modify files, delete data, or trigger external operations. This is a straightforward listing operation similar to 'list' or 'get', placing it in the Read category with low severity due to minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'List the yaver-test-sdk specs' and 'Returns name, path, target, step count' — purely a retrieval/query operation with no modification or execution of tests.
Attacks that exploit this kind of access
The rule that runs testkit_list_specs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For testkit_list_specs, this is the rule to start with:
testkit_list_specs 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 Yaver, apply this rule, and every testkit_list_specs call is checked against it from then on.
Questions about testkit_list_specs
List the yaver-test-sdk specs in the current project (yaver-tests//*.test.yaml). Returns name, path, target, step count. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
testkit_list_specs accepts 1 parameter: root. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for testkit_list_specs: 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 Yaver. Nothing to install.
testkit_list_specs 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 testkit_list_specs 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 testkit_list_specs. 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.
testkit_list_specs is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue