Returns superfluid staking module parameters
AI agents call get-superfluid-params to retrieve information from Osmosis MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to fetch blockchain module parameters. It retrieves existing data with no side effects, no state changes, and no ability to modify or delete data. It falls squarely within the Read category. The severity is low because parameter queries pose minimal risk—they cannot be misused to cause harm even if an AI agent invokes them arbitrarily.
From the tool's definition Tool name 'get-superfluid-params' and description 'Returns superfluid staking module parameters' indicate a query operation that retrieves configuration data without modification or execution of transactions.
Attacks that exploit this kind of access
Returns superfluid staking module parameters. It is categorised as a Read tool in the Osmosis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Osmosis MCP Server MCP server in PolicyLayer and add a rule for get-superfluid-params: 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 Osmosis MCP Server. Nothing to install.
get-superfluid-params 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-superfluid-params 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-superfluid-params. 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-superfluid-params is provided by the Osmosis MCP Server MCP server (myronkoch-dev/mcp-osmosis). 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 →