Search official SAPUI5 SDK metadata and return API/topic summaries with examples.
AI agents call search_ui5_sdk to retrieve information from MCP SAPUI5 Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information from official SAPUI5 SDK documentation and API metadata. It performs no data modification, deletion, code execution, or external side effects. The action is purely informational retrieval with no blast radius if misused—an agent might return incorrect documentation but cannot damage systems, data, or finances.
From the tool's definition Tool name 'search_ui5_sdk' and description 'Search official SAPUI5 SDK metadata and return API/topic summaries with examples' indicate a retrieval operation against read-only documentation/metadata sources.
Attacks that exploit this kind of access
Search official SAPUI5 SDK metadata and return API/topic summaries with examples. It is categorised as a Read tool in the MCP SAPUI5 Server MCP Server, which means it retrieves data without modifying state.
Register the MCP SAPUI5 Server MCP server in PolicyLayer and add a rule for search_ui5_sdk: 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 MCP SAPUI5 Server. Nothing to install.
search_ui5_sdk 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_ui5_sdk 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_ui5_sdk. 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_ui5_sdk is provided by the MCP SAPUI5 Server MCP server (santiagosanmartinn/mcpui5server). 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 →