project_profile

Detect the project's framework, product/host type, providers, deploy targets, preview surfaces, and project-scoped MCP adapter policy. Read-only; credentials are never returned.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/project-profile.md

WHAT IT DOES

What project_profile does on Yaver

AI agents call project_profile 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	—	Project directory. Omit to use the agent's configured work directory.

Parameters from the server's own tool schema.

RISK

Why project_profile is rated Low

Tool only detects and returns project metadata without any side effects.

From the tool's definition Read-only; credentials are never returned

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs project_profile 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_profile, this is the rule to start with:

project_profile Allowed

project_profile is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "project_profile": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every project_profile call is checked against it from then on.

FAQ

Questions about project_profile

What does the project_profile tool do? +

Detect the project's framework, product/host type, providers, deploy targets, preview surfaces, and project-scoped MCP adapter policy. Read-only; credentials are never returned. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does project_profile accept? +

project_profile accepts 1 parameter: directory. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on project_profile? +

Register the Yaver MCP server in PolicyLayer and add a rule for project_profile: 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.

What risk level is project_profile? +

project_profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit project_profile? +

Yes. Add a rate_limit block to the project_profile 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 project_profile completely? +

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

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

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 678 Yaver tools →

Across the catalogue

index_project on ACE-MCP → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →