get_current_organization_info
Get information about the current user and organization based on the token. In the absence of an explicitly specified organization ID, this result will take precedence.
This record as markdown: /tools/alibabacloud-devops/get-current-organization-info.md
What get_current_organization_info does on Alibabacloud Devops
AI agents call get_current_organization_info to retrieve information from Alibabacloud Devops without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_current_organization_info is rated Low
This is a read-only query operation that retrieves metadata about the current user and organization context. It has minimal blast radius - an AI agent calling this tool cannot cause harm beyond potentially accessing user/org information it may already have access to through its authentication token. Classification as Read is appropriate.
From the tool's definition The tool description states it 'Get[s] information about the current user and organization' - a retrieval operation with no side effects. No creation, modification, deletion, or execution is performed.
Attacks that exploit this kind of access
The rule that runs get_current_organization_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Alibabacloud Devops, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_current_organization_info, this is the rule to start with:
get_current_organization_info 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 Alibabacloud Devops, apply this rule, and every get_current_organization_info call is checked against it from then on.
Questions about get_current_organization_info
Get information about the current user and organization based on the token. In the absence of an explicitly specified organization ID, this result will take precedence. It is categorised as a Read tool in the Alibabacloud Devops MCP Server, which means it retrieves data without modifying state.
Register the Alibabacloud Devops MCP server in PolicyLayer and add a rule for get_current_organization_info: 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 Alibabacloud Devops. Nothing to install.
get_current_organization_info 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_current_organization_info 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_current_organization_info. 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_current_organization_info is provided by the Alibabacloud Devops MCP server (alibabacloud-devops-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Alibabacloud Devops, and thousands of servers like it.
This server
Across the catalogue