AI agents call sim_marketplace_info_tool to retrieve information from Robotics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name indicates an informational lookup ('info') in a marketplace context, which typically retrieves data without modification. However, confidence is moderate due to the empty description and lack of explicit confirmation that this tool is read-only. The context of a robotics/simulation server suggests it queries available robots, models, or services in a marketplace, consistent with Read operations.
From the tool's definition Tool name 'sim_marketplace_info_tool' suggests retrieval of marketplace information. Description is empty, providing no additional details about functionality.
Documented attack patterns abuse exactly the kind of access sim_marketplace_info_tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Robotics MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for sim_marketplace_info_tool:
{
"version": "1",
"default": "deny",
"tools": {
"sim_marketplace_info_tool": {}
}
}sim_marketplace_info_tool is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
sim_marketplace_info_tool. It is categorised as a Read tool in the Robotics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Robotics MCP Server MCP server in PolicyLayer and add a rule for sim_marketplace_info_tool: 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 Robotics MCP Server. Nothing to install.
sim_marketplace_info_tool 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 sim_marketplace_info_tool 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 sim_marketplace_info_tool. 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.
sim_marketplace_info_tool is provided by the Robotics MCP Server MCP server (sandraschi/robotics-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Robotics MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Robotics MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.