Returns synthetic lock details by underlying lock ID
AI agents call get-synthetic-locks-by-lock-id 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 retrieves and returns data about synthetic locks without modifying, executing, or destructing any blockchain state. It is a read-only query operation. Despite operating on a blockchain with financial implications, the tool itself performs no financial transactions, execution, or data modification.
From the tool's definition Tool name includes 'get-' prefix and description states 'Returns synthetic lock details', indicating a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Returns synthetic lock details by underlying lock ID. 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-synthetic-locks-by-lock-id: 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-synthetic-locks-by-lock-id 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-synthetic-locks-by-lock-id 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-synthetic-locks-by-lock-id. 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-synthetic-locks-by-lock-id 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 →