AI agents call get_portal_status to retrieve information from Datagovma without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves portal status information from the Moroccan Open Data portal without creating, modifying, deleting, or executing any operations. The GET prefix and status query pattern are characteristic of Read operations. Confidence is slightly reduced due to the empty description, but the context of an open data portal and naming pattern strongly indicate this is informational retrieval only.
From the tool's definition Tool name 'get_portal_status' indicates a retrieval operation. The description is empty, but the naming convention and sibling tools (all get_*, list_*, search_* operations on a data portal) establish this as a query-only function that retrieves status…
Attacks that exploit this kind of access
get_portal_status. It is categorised as a Read tool in the Datagovma MCP Server, which means it retrieves data without modifying state.
Register the Datagovma MCP server in PolicyLayer and add a rule for get_portal_status: 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 Datagovma. Nothing to install.
get_portal_status 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_portal_status 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_portal_status. 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_portal_status is provided by the Datagovma MCP server (mohtamimad/datagovma-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 →