get_fact
Get a single verified fact for a company by domain and fact key (e.g. "tagline", "description").
This record as markdown: /tools/com-groundedaeo-grounded-aeo/get-fact.md
What get_fact does on Grounded Aeo
AI agents call get_fact to retrieve information from Grounded Aeo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | Fact key, e.g. "tagline" |
domain | string | Yes |
Parameters from the server's own tool schema.
Why get_fact is rated Low
This tool retrieves existing company metadata (facts like tagline or description) indexed by domain and fact key. It performs a lookup query with no ability to modify, create, delete, or execute operations. The blast radius of misuse is minimal—an agent could retrieve facts about arbitrary companies, but this poses no data integrity, security, or operational risk. Classified as Read with low severity.
From the tool's definition Tool description states 'Get a single verified fact for a company' — a retrieval operation with no modification, deletion, or execution. The verb 'get' and lack of side-effects confirm read-only semantics.
Attacks that exploit this kind of access
The rule that runs get_fact safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Grounded Aeo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_fact, this is the rule to start with:
get_fact is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Grounded Aeo, apply this rule, and every get_fact call is checked against it from then on.
Questions about get_fact
Get a single verified fact for a company by domain and fact key (e.g. "tagline", "description"). It is categorised as a Read tool in the Grounded Aeo MCP Server, which means it retrieves data without modifying state.
get_fact accepts 2 parameters: key, domain. Required: key, domain. The full parameter table on this page comes from the server's own tool schema.
Register the Grounded Aeo MCP server in PolicyLayer and add a rule for get_fact: 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 Grounded Aeo. Nothing to install.
get_fact 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_fact 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_fact. 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_fact is provided by the Grounded Aeo MCP server (https://groundedaeo.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Grounded Aeo, and thousands of servers like it.
This server
Across the catalogue