AI agents call call_api as a supporting operation in Document Loader MCP Server workflows.
The description is empty and the tool name 'call_api' is too generic to determine what it does. In the context of a document parsing server (AWS Labs MCP), it may invoke a document parsing API (Read), but without evidence it could also Write or Execute. Confidence is very low. Defaulting to Other due to insufficient information, with medium severity given the ambiguity.
From the tool's definition Tool name is 'call_api' with an empty description. No information about what API is called or what effects it has.
Documented attack patterns abuse exactly the kind of access call_api gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Document Loader MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for call_api:
{
"version": "1",
"default": "deny",
"tools": {
"call_api": {
"limits": [
{
"counter": "call_api_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}call_api gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
call_api. It is categorised as a Other tool in the Document Loader MCP Server MCP Server, which means it performs auxiliary operations.
Register the Document Loader MCP Server MCP server in PolicyLayer and add a rule for call_api: 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 Document Loader MCP Server. Nothing to install.
call_api is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the call_api 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 call_api. 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.
call_api is provided by the Document Loader MCP Server MCP server (awslabs.document-loader-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Document Loader 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.
805 Document Loader MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.