au-data-gov.reference.organization_search
Look up Australian federal/state/territory agencies and organizations publishing on the open data portal by name, returning id, slug, and title. Use the returned slug as the organization filter for au-data-gov.dataset_search. Data: data.gov.au CKAN Action API, no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/au-data-gov.reference.organization-search.md
What au-data-gov.reference.organization_search does on Apibase
AI agents call au-data-gov.reference.organization_search to retrieve information from Apibase 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 |
|---|---|---|---|
limit | integer | — | Max organizations to return (1-50, default 20) |
query | string | — | Free-text search on organization name/title (e.g. "health") |
Parameters from the server's own tool schema.
Why au-data-gov.reference.organization_search is rated Low
Queries public Australian government organization metadata without side effects or access restrictions.
From the tool's definition Look up organizations, returns id/slug/title, no auth required
Attacks that exploit this kind of access
The rule that runs au-data-gov.reference.organization_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For au-data-gov.reference.organization_search, this is the rule to start with:
au-data-gov.reference.organization_search 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 Apibase, apply this rule, and every au-data-gov.reference.organization_search call is checked against it from then on.
Questions about au-data-gov.reference.organization_search
Look up Australian federal/state/territory agencies and organizations publishing on the open data portal by name, returning id, slug, and title. Use the returned slug as the organization filter for au-data-gov.dataset_search. Data: data.gov.au CKAN Action API, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
au-data-gov.reference.organization_search accepts 2 parameters: limit, query. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for au-data-gov.reference.organization_search: 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 Apibase. Nothing to install.
au-data-gov.reference.organization_search 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 au-data-gov.reference.organization_search 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 au-data-gov.reference.organization_search. 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.
au-data-gov.reference.organization_search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue