ABAP FEATURE MATRIX: abap_feature_matrix(query=
AI agents call abap_feature_matrix 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 retrieves feature matrix information based on a query parameter. It has no mechanism to modify, delete, or execute code—it only queries and returns reference data. The blast radius of misuse is minimal; an agent could only retrieve potentially sensitive architectural information about ABAP features, not alter systems or execute operations.
From the tool's definition Tool name 'abap_feature_matrix' with description prefix 'ABAP FEATURE MATRIX' and invocation pattern 'query=' indicates a lookup/retrieval operation.
Documented attack patterns abuse exactly the kind of access abap_feature_matrix 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 abap_feature_matrix:
{
"version": "1",
"default": "deny",
"tools": {
"abap_feature_matrix": {}
}
} abap_feature_matrix 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.
ABAP FEATURE MATRIX: abap_feature_matrix(query=. 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 abap_feature_matrix: 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.
abap_feature_matrix 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 abap_feature_matrix 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 abap_feature_matrix. 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.
abap_feature_matrix 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.