Search for datasets on Morocco
AI agents call search_datasets to retrieve information from Morocco Open Data MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a search/query operation that retrieves information about available datasets. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger external operations. It fits squarely within the Read category—the lowest risk, as it only retrieves metadata about datasets without accessing sensitive data directly or performing any state-changing operations.
From the tool's definition Tool name 'search_datasets' and description 'Search for datasets on Morocco' indicate a query operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Search for datasets on Morocco. It is categorised as a Read tool in the Morocco Open Data MCP MCP Server, which means it retrieves data without modifying state.
Register the Morocco Open Data MCP server in PolicyLayer and add a rule for search_datasets: 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 Morocco Open Data MCP. Nothing to install.
search_datasets 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 search_datasets 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 search_datasets. 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.
search_datasets is provided by the Morocco Open Data MCP server (kcbdev/morocco-open-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →