This record as markdown: /tools/io-github-kivanccakmak-yaver/convex-schema.md
What convex_schema does on Yaver
AI agents call convex_schema 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 convex_schema is rated Low
This tool retrieves and displays configuration/schema information from a project without modifying, executing, or deleting anything. It is purely informational (Read category). The severity is low because schema files are typically non-sensitive project metadata, and misuse would only expose structural information about the database, not sensitive data or enable harmful actions.
From the tool's definition The tool 'convex_schema' shows/displays the Convex schema.ts file for a project. The verb 'show' and the act of retrieving/reading a schema file indicate a read-only operation with no side effects.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs convex_schema 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 convex_schema, this is the rule to start with:
convex_schema 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 convex_schema call is checked against it from then on.
Questions about convex_schema
Show the Convex schema.ts for a project. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
convex_schema 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 convex_schema: 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.
convex_schema 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 convex_schema 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 convex_schema. 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.
convex_schema 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