Tool requests
Anyone on your staff can ask for an AI tool or an MCP server. An administrator approves or denies the request. This page covers how staff ask, how you decide, who is told, and how to take requests…
Written By Christopher Scaminaci
Last updated 4 days ago
Anyone on your staff can ask for an AI tool or an MCP server. An administrator approves or denies the request. This page covers how staff ask, how you decide, who is told, and how to take requests from Microsoft Teams with a workflow.
At a glance
- What it does: gives staff a way to ask, and gives you a queue to decide.
- Plan: every plan. The Teams approval buttons need Pro. See Approve AI tool requests from Teams.
- Who: staff ask. An Administrator decides. Reviewers and auditors read the page.
- Where: AI Governance → AI inventory → Tool requests.
- Needs: nothing. Staff can use the Portal or their personal link page.
Asking
Anyone on your staff can ask for an AI tool or an MCP server: from the Portal, from their personal link page, or from Microsoft Teams. A request needs the tool's name and a reason of at least 10 characters. One person can make ten requests a day. A request puts the tool in your inventory as "Waiting for a decision", marked as requested by staff.
Deciding
An Administrator opens the request from Tool requests and selects Approve or Deny in the Decide panel of the request's own page. A Reason is optional; the person sees it in the decision email and on their own page. The "A tool request is waiting" alert in Teams opens Tool requests. Approving marks that inventory item Approved and puts it on your approved lists. Denying marks it Denied. If settings are delivered to staff machines, the new lists go out with the next push.
You can also approve or deny from your AI tool, or from a Teams card. The decision is the same everywhere.
Who is told
- A person who asked from the Portal is emailed the decision and the reason.
- A person who asked from their personal link page is emailed too, at the address your staff list holds for them. If it holds none, the decision shows on their own page only.
- A request that came through Teams is not emailed, because Teams cannot prove who sent it and the address could be anyone's. A request sent from Teams is marked "via Teams (email not verified)" so the approver knows.
In every case the decision also shows on the person's own page.
Take requests from Microsoft Teams with a workflow
You can send requests from a Teams workflow to StackJack. The Teams bot with approval buttons is a separate option. See Approve AI tool requests from Teams.
Set it up once. In Teams, build a workflow that sends each request to a private web address. StackJack shows the address and a secret once, on the Requests page. Copy both into the workflow now, because the secret is not shown again. If you lose it, rotate it. The old one stops at once.
In the workflow, add an HTTP action:
- Method: POST.
- Address: the private web address from the Requests page.
- Header
X-StackJack-Intake-Key: the secret. - Body, as JSON:
{ "email": "person@yourcompany.com", "tool": "Name of the tool", "url": "https://example.com", "reason": "Why they need it" }. Theurlis optional. To ask for an MCP server, add"kind": "mcp-server".
What comes back.
Be careful who can send. Teams cannot prove who asked, so every request that arrives this way is marked "via Teams (email not verified)". Build the workflow so only people you trust can start it. The setup page says when this lane is not switched on for your region yet. You can prepare it, and it starts working once StackJack turns it on.
What you will see
- A queue of requests with status.
- The tool in AI inventory → Inventory as "Waiting for a decision".
- An "Approval requested" alert in the inbox.
Troubleshooting
Next
Was this helpful?
More in Control and respond
Rule packs, modes and custom rulesFindings and triageData-loss rules, findings and scanning StackJack tool trafficFilter personal data out of tool results (the PII filter)Still need help? Ask the team