AI agents call get_defaults 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 tool name and the pattern of sibling tools on this server (all read-only settings discovery operations), 'get_defaults' most likely retrieves default values without modifying data. No evidence of side effects, execution, or destructive capability. The empty description prevents higher confidence, but the naming convention and context strongly indicate a Read operation with minimal risk.
From the tool's definition Tool name 'get_defaults' suggests retrieval of default configuration values; sibling tools 'list_settings', 'lookup_setting', and 'search_settings' are all Read operations on settings. Description is empty, which reduces confidence slightly.
Attacks that exploit this kind of access
get_defaults. 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 get_defaults: 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.
get_defaults 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_defaults 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_defaults. 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_defaults 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 →