project_runtime
Summarize project runtime placement, export targets, provider requirements, and machine resolution for the current monorepo or project.
This record as markdown: /tools/io-github-kivanccakmak-yaver/project-runtime.md
What project_runtime does on Yaver
AI agents call project_runtime 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 |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why project_runtime is rated Low
This tool retrieves and reports configuration information about a project's runtime setup without modifying state, executing code, or triggering external operations. It is purely informational, making it a Read category tool with low severity as misuse would only expose project metadata.
From the tool's definition Tool description states it 'Summarize[s]' and describes retrieval of project configuration details (runtime placement, export targets, provider requirements, machine resolution).
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs project_runtime 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 project_runtime, this is the rule to start with:
project_runtime 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 project_runtime call is checked against it from then on.
Questions about project_runtime
Summarize project runtime placement, export targets, provider requirements, and machine resolution for the current monorepo or project. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
project_runtime accepts 1 parameter: directory. 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 project_runtime: 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.
project_runtime 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 project_runtime 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 project_runtime. 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.
project_runtime 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