AI agents call lookup_setting to retrieve information from Wiswa without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the context of sibling tools and the server's purpose of exposing settings discovery, 'lookup_setting' most likely retrieves or queries settings data without modifying state. The absence of a description lowers confidence slightly, but the naming pattern and server purpose strongly suggest a read-only operation with minimal blast radius if misused.
From the tool's definition Tool name 'lookup_setting' combined with sibling tools 'get_defaults', 'list_settings', and 'search_settings' indicates data retrieval operations. The server exposes 'Wiswa settings discovery', which is informational in nature.
Attacks that exploit this kind of access
lookup_setting. It is categorised as a Read tool in the Wiswa MCP Server, which means it retrieves data without modifying state.
Register the Wiswa MCP server in PolicyLayer and add a rule for lookup_setting: 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 Wiswa. Nothing to install.
lookup_setting 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 lookup_setting 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 lookup_setting. 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.
lookup_setting is provided by the Wiswa MCP server (tatsh/wiswa-mcp). 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 →