New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

jira_search_users

Search for Jira users

SERVERSage MCP SOURCEsagemcp/sagemcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/jira-search-users.md

What jira_search_users does on Sage MCP

AI agents call jira_search_users to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why jira_search_users is rated Low

This tool performs a search/query operation to retrieve Jira user data. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger external operations. It falls squarely into the Read category. The severity is low because user directory searches are typically low-risk operations with limited blast radius even if misused by an agent.

From the tool's definition Tool name 'jira_search_users' and description 'Search for Jira users' indicate a query operation that retrieves user information without modifying data.

Questions about jira_search_users

What does the jira_search_users tool do? +

Search for Jira users. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on jira_search_users? +

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

What risk level is jira_search_users? +

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

Can I rate-limit jira_search_users? +

Yes. Add a rate_limit block to the jira_search_users 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 jira_search_users completely? +

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

jira_search_users is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Sage, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sage's. Pull the full record:

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.