Get current configuration (API key masked).
AI agents call get_config to retrieve information from Screenshot Analyzer MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves configuration data as a read operation. Although it accesses sensitive configuration information (API keys, though masked), it does not modify state, execute code, or cause side effects. The masking of the API key further reduces the sensitivity of exposed information.
From the tool's definition Tool name is 'get_config' and description states it retrieves 'current configuration (API key masked)'. This is a read-only operation that queries configuration state without modifying, executing external operations, or deleting anything.
Attacks that exploit this kind of access
Get current configuration (API key masked). It is categorised as a Read tool in the Screenshot Analyzer MCP MCP Server, which means it retrieves data without modifying state.
Register the Screenshot Analyzer MCP server in PolicyLayer and add a rule for get_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 Screenshot Analyzer MCP. Nothing to install.
get_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 get_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 get_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.
get_config is provided by the Screenshot Analyzer MCP server (sasuke-inu/ui-screenshot-android-review-openai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →