get_reporting_chain_up

Walk the management chain upward from the given person. Returns an ordered list starting with the person and ending at the top of the chain (someone with no manager).

Server Humaans ptorsten/humaans-mcp
Category Read
Risk class Low
Parameters 00 required

What get_reporting_chain_up does on Humaans

AI agents call get_reporting_chain_up to retrieve information from Humaans without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_reporting_chain_up needs a policy

This tool retrieves organizational hierarchy data by traversing manager relationships. It queries and returns information without modifying any state. The read-only nature of the server and the purely informational purpose of the tool (returning a list of people in the reporting chain) make this a straightforward Read category tool with low severity.

From the tool's definition Tool description states it 'Walk[s] the management chain upward' and 'Returns an ordered list', which are read-only query operations. Server is explicitly described as 'Read-only MCP server'. No mutations, deletions, or side effects are performed.

Questions about get_reporting_chain_up

What does the get_reporting_chain_up tool do? +

Walk the management chain upward from the given person. Returns an ordered list starting with the person and ending at the top of the chain (someone with no manager). It is categorised as a Read tool in the Humaans MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_reporting_chain_up? +

Register the Humaans MCP server in PolicyLayer and add a rule for get_reporting_chain_up: 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 Humaans. Nothing to install.

What risk level is get_reporting_chain_up? +

get_reporting_chain_up is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_reporting_chain_up? +

Yes. Add a rate_limit block to the get_reporting_chain_up 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.

How do I block get_reporting_chain_up completely? +

Set action: deny in the PolicyLayer policy for get_reporting_chain_up. 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.

What MCP server provides get_reporting_chain_up? +

get_reporting_chain_up is provided by the Humaans MCP server (ptorsten/humaans-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.