Get a direct answer to a question about MCP servers, local AI, or AI automation from ASTGL's knowledge base. Returns the best matching answer with source URL and related articles.
AI agents call get_answer to retrieve information from ASTGL Knowledge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
question | string | Yes | A specific question (e.g., 'What is an MCP server?') |
content_type | string | — | Filter by content type: article, tutorial, faq, comparison, guide, newsletter, project |
Parameters from the server's own tool schema.
This tool retrieves and returns information from a knowledge base without modifying state, executing arbitrary code, or triggering external side effects. It is a straightforward search/query tool that merely fetches and presents pre-existing content.
From the tool's definition Tool description explicitly states it 'Get[s] a direct answer' and 'Returns the best matching answer' with citations—a read-only retrieval operation. No modification, deletion, code execution, or financial impact is implied.
Documented attack patterns abuse exactly the kind of access get_answer gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ASTGL Knowledge, and nothing reaches the server without passing your rules. This is the rule we recommend for get_answer:
{
"version": "1",
"default": "deny",
"tools": {
"get_answer": {}
}
}get_answer 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 a direct answer to a question about MCP servers, local AI, or AI automation from ASTGL's knowledge base. Returns the best matching answer with source URL and related articles. It is categorised as a Read tool in the ASTGL Knowledge MCP Server, which means it retrieves data without modifying state.
get_answer accepts 2 parameters: question, content_type. Required: question. The full parameter table on this page comes from the server's own tool schema.
Register the ASTGL Knowledge MCP server in PolicyLayer and add a rule for get_answer: 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 ASTGL Knowledge. Nothing to install.
get_answer 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 get_answer 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 get_answer. 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.
get_answer is provided by the ASTGL Knowledge MCP server (mcp-astgl-knowledge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ASTGL Knowledge, 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 ASTGL Knowledge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.