Switch the active SOLAPI credential profile.
AI agents use configure_use to create or update resources in SOLAPI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SOLAPI MCP Server environment.
This tool changes configuration state reversibly by switching between credential profiles. It does not delete data (Destructive), execute arbitrary code (Execute), or transfer money (Financial). However, it is not purely Read since it modifies active state.
From the tool's definition Tool description states 'Switch the active SOLAPI credential profile' — this modifies application state by changing which credential set is active, affecting subsequent message sending operations.
Attacks that exploit this kind of access
Switch the active SOLAPI credential profile. It is categorised as a Write tool in the SOLAPI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SOLAPI MCP Server MCP server in PolicyLayer and add a rule for configure_use: 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 SOLAPI MCP Server. Nothing to install.
configure_use is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the configure_use 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 configure_use. 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.
configure_use is provided by the SOLAPI MCP Server MCP server (solapi/solapi-mcp-server). 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 →