phone_project_get
Get the full metadata for one phone project — schema, auth, seed, live table/row stats.
This record as markdown: /tools/io-github-kivanccakmak-yaver/phone-project-get.md
What phone_project_get does on Yaver
AI agents call phone_project_get 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 |
|---|---|---|---|
slug | string | Yes |
Parameters from the server's own tool schema.
Why phone_project_get is rated Low
This tool queries and retrieves project metadata only. The verb 'Get' and the absence of any create/modify/delete/execute language indicates a read-only operation. Metadata retrieval carries minimal risk unless the auth credentials returned are sensitive, but the baseline category is Read. Severity is low because reading project metadata does not alter system state or trigger external operations.
From the tool's definition Tool description states 'Get the full metadata for one phone project' — explicitly a retrieval action with no side effects. Returns schema, auth, seed, and stats data without modification or execution.
Attacks that exploit this kind of access
The rule that runs phone_project_get 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 phone_project_get, this is the rule to start with:
phone_project_get 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 phone_project_get call is checked against it from then on.
Questions about phone_project_get
Get the full metadata for one phone project — schema, auth, seed, live table/row stats. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
phone_project_get accepts 1 parameter: slug. Required: slug. 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 phone_project_get: 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.
phone_project_get 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 phone_project_get 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 phone_project_get. 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.
phone_project_get 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