app_get_status

A read tool on the Eda Agent MCP server.

SERVEREda Agent SOURCEsalitronic/eda-agent

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eda-agent/app-get-status.md

WHAT IT DOES

What app_get_status does on Eda Agent

AI agents call app_get_status to retrieve information from Eda Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why app_get_status is rated Low

Based on the naming convention (app_get_*) and context of sibling get operations that retrieve application state and metadata, this tool appears to query current application status without modification. No side effects or destructive operations implied. The empty description lowers confidence slightly, but the 'get_' prefix is a strong signal for Read operations.

From the tool's definition Tool name 'app_get_status' with 'get' prefix and sibling tools like 'app_get_active_document', 'app_get_clipboard', 'app_get_preferences', 'app_get_report', 'app_get_version' all indicate query/retrieval operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs app_get_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Eda Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For app_get_status, this is the rule to start with:

app_get_status Allowed

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

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

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

FAQ

Questions about app_get_status

What does the app_get_status tool do? +

app_get_status is a read tool on the Eda Agent MCP server. It is categorised as a Read tool in the Eda Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on app_get_status? +

Register the Eda Agent MCP server in PolicyLayer and add a rule for app_get_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 Eda Agent. Nothing to install.

What risk level is app_get_status? +

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

Can I rate-limit app_get_status? +

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

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

app_get_status is provided by the Eda Agent MCP server (salitronic/eda-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Eda Agent, and thousands of servers like it.

This server

All 345 Eda Agent tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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