expo_status

Show Expo project config.

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/expo-status.md

WHAT IT DOES

What expo_status does on Yaver

AI agents call expo_status 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.

RISK

Why expo_status is rated Low

This tool retrieves and displays Expo project configuration information. It is a read-only operation with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an agent could only learn about the project's configuration settings. This is clearly a Read category tool.

From the tool's definition Tool name 'expo_status' and description 'Show Expo project config' indicate a query operation that retrieves configuration data without modifying or executing anything.

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

expo_status Allowed

expo_status 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": {
    "expo_status": {}
  }
}

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 expo_status call is checked against it from then on.

FAQ

Questions about expo_status

What does the expo_status tool do? +

Show Expo project config. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does expo_status accept? +

expo_status 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 expo_status? +

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

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

Can I rate-limit expo_status? +

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

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

expo_status 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 645 Yaver tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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