Fetch rows from a knowledge list (paginated, up to 200 per call). Use this to inspect actual data or scan a small list end-to-end. Returns rows with their full rowData, count, totalCount for unfiltered list reads, and nextToken. Pass nextToken from the previous response to fetch the next page. ne...
Part of the Agentled server.
Free to start. No card required.
AI agents call get_knowledge_rows to retrieve information from Agentled without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_knowledge_rows only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_knowledge_rows": {}
}
}See the full Agentled policy for all 119 tools.
These attack patterns abuse exactly the kind of access get_knowledge_rows gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Fetch rows from a knowledge list (paginated, up to 200 per call). Use this to inspect actual data or scan a small list end-to-end. Returns rows with their full rowData, count, totalCount for unfiltered list reads, and nextToken. Pass nextToken from the previous response to fetch the next page. nextToken is null when there are no more rows. For targeted lookups by ID use get_knowledge_rows_by_ids — it fetches specific rows in a single call (max 200) without scanning the whole list. For entity-relationship queries (e.g. "all deals scored by this investor") start with query_kg_edges, then pass the returned node IDs to get_knowledge_rows_by_ids.. It is categorised as a Read tool in the Agentled MCP Server, which means it retrieves data without modifying state.
Register the Agentled MCP server in PolicyLayer and add a rule for get_knowledge_rows: 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 Agentled. Nothing to install.
get_knowledge_rows 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_knowledge_rows 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_knowledge_rows. 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_knowledge_rows is provided by the Agentled MCP server (@agentled/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 119 Agentled tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.