Search for API operations by name, path, or description
AI agents call search_operations to retrieve information from 3dspace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available API operations without modifying, executing, or deleting any data. It is purely informational—helping users discover which operations exist in the 3DSpace Engineering Web Services APIs. No data is created, modified, or destroyed, and no external code is executed as a result of using this tool.
From the tool's definition Tool performs a search operation to find API operations by name, path, or description. The verb 'search' and the search parameters (name, path, description) indicate a query/retrieval function with no side effects.
Documented attack patterns abuse exactly the kind of access search_operations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 3dspace, and nothing reaches the server without passing your rules. This is the rule we recommend for search_operations:
{
"version": "1",
"default": "deny",
"tools": {
"search_operations": {}
}
}search_operations 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.
Search for API operations by name, path, or description. It is categorised as a Read tool in the 3dspace MCP Server, which means it retrieves data without modifying state.
Register the 3dspace MCP server in PolicyLayer and add a rule for search_operations: 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 3dspace. Nothing to install.
search_operations 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 search_operations 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 search_operations. 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.
search_operations is provided by the 3dspace MCP server (pgupta1795/3dspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 3dspace, 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.
7 3dspace tools catalogued and risk-classified — across an index of 43,000+ MCP servers.