GET SAP BTP SERVICE DETAILS: sap_discovery_center_service(serviceId=
AI agents call sap_discovery_center_service to retrieve information from Abap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves service details from SAP's discovery center using a service identifier. The 'GET' verb and retrieval-focused operation place it squarely in the Read category. There is no indication of write, execute, destructive, or financial operations. The blast radius is minimal—it only exposes publicly available service metadata.
From the tool's definition Tool description indicates 'GET SAP BTP SERVICE DETAILS' with a serviceId parameter, describing a retrieval operation with no modification, deletion, or execution capabilities indicated.
Documented attack patterns abuse exactly the kind of access sap_discovery_center_service gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Abap, and nothing reaches the server without passing your rules. This is the rule we recommend for sap_discovery_center_service:
{
"version": "1",
"default": "deny",
"tools": {
"sap_discovery_center_service": {}
}
} sap_discovery_center_service 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.
GET SAP BTP SERVICE DETAILS: sap_discovery_center_service(serviceId=. It is categorised as a Read tool in the Abap MCP Server, which means it retrieves data without modifying state.
Register the Abap MCP server in PolicyLayer and add a rule for sap_discovery_center_service: 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 Abap. Nothing to install.
sap_discovery_center_service 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 sap_discovery_center_service 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 sap_discovery_center_service. 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.
sap_discovery_center_service is provided by the Abap MCP server (marianfoo/abap-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Abap, 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.
8 Abap tools catalogued and risk-classified — across an index of 43,000+ MCP servers.