app_get_preferences
A read tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/app-get-preferences.md
What app_get_preferences does on Eda Agent
AI agents call app_get_preferences 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.
Why app_get_preferences is rated Low
This tool retrieves application preferences without modifying state. The 'get_' prefix consistently indicates read operations across the sibling tool set. While the description is uninformative, the naming convention and context strongly suggest a non-destructive query. Confidence is slightly reduced due to lack of explicit documentation, but the risk remains low even if preferences contain configuration data.
From the tool's definition Tool name 'app_get_preferences' indicates a retrieval operation ('get') with no modification capability. The empty description prevents confirmation of data sensitivity, but the naming pattern aligns with read-only query tools alongside sibling tools like…
Attacks that exploit this kind of access
The rule that runs app_get_preferences 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_preferences, this is the rule to start with:
app_get_preferences 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 Eda Agent, apply this rule, and every app_get_preferences call is checked against it from then on.
Questions about app_get_preferences
app_get_preferences 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.
Register the Eda Agent MCP server in PolicyLayer and add a rule for app_get_preferences: 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.
app_get_preferences 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 app_get_preferences 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 app_get_preferences. 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.
app_get_preferences 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.
More on Eda Agent, and thousands of servers like it.
This server
Across the catalogue