storage_config
Get S3-compatible config for app integration (endpoint, access key, secret key).
This record as markdown: /tools/io-github-kivanccakmak-yaver/storage-config.md
What storage_config does on Yaver
AI agents call storage_config 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.
Why storage_config is rated Low
This tool retrieves sensitive configuration (S3 endpoint, access key, secret key) but does not modify, execute, or delete anything. It is categorized as Read because the primary action is data retrieval.
From the tool's definition Tool name 'storage_config' and description 'Get S3-compatible config for app integration (endpoint, access key, secret key)' indicate retrieval of configuration data.
Attacks that exploit this kind of access
The rule that runs storage_config 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 storage_config, this is the rule to start with:
storage_config 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 storage_config call is checked against it from then on.
Questions about storage_config
Get S3-compatible config for app integration (endpoint, access key, secret key). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for storage_config: 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.
storage_config 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 storage_config 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 storage_config. 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.
storage_config 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