AI agents call describe_endpoint to retrieve information from J Quants Doc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and presents API endpoint documentation. The empty description reduces confidence slightly, but the name and server context strongly suggest a read-only information retrieval function. Severity is medium rather than low due to the potential for an AI agent to misuse detailed endpoint documentation to craft malicious API requests, though the tool itself performs no side effects.
From the tool's definition Tool is a sibling to fetch_spec_page, get_info, search_endpoints, and get_pattern on a documentation/API reference server.
Documented attack patterns abuse exactly the kind of access describe_endpoint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and J Quants Doc, and nothing reaches the server without passing your rules. This is the rule we recommend for describe_endpoint:
{
"version": "1",
"default": "deny",
"tools": {
"describe_endpoint": {}
}
}describe_endpoint 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.
describe_endpoint. It is categorised as a Read tool in the J Quants Doc MCP Server, which means it retrieves data without modifying state.
Register the J Quants Doc MCP server in PolicyLayer and add a rule for describe_endpoint: 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 J Quants Doc. Nothing to install.
describe_endpoint 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 describe_endpoint 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 describe_endpoint. 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.
describe_endpoint is provided by the J Quants Doc MCP server (j-quants/j-quants-doc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from J Quants Doc, 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 J Quants Doc tools catalogued and risk-classified — across an index of 43,000+ MCP servers.