Decode hidden states back to SMILES strings. Converts MolMIM
AI agents invoke molmim_decode to trigger actions in MolMIM MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool runs a computational operation (decoding hidden states) against an external API. It neither reads stored data nor writes/modifies persistent data — it executes a transformation process. The blast radius is low as it only produces molecular string outputs with no side effects on data or systems.
From the tool's definition 'Decode hidden states back to SMILES strings. Converts MolMIM' — triggers a computational transformation via the NVIDIA MolMIM API, converting internal representations to molecular SMILES strings
Attacks that exploit this kind of access
Decode hidden states back to SMILES strings. Converts MolMIM. It is categorised as a Execute tool in the MolMIM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MolMIM MCP Server MCP server in PolicyLayer and add a rule for molmim_decode: 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 MolMIM MCP Server. Nothing to install.
molmim_decode is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the molmim_decode 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 molmim_decode. 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.
molmim_decode is provided by the MolMIM MCP Server MCP server (siarhei-fedziukovich/mcp-molmim). 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 →