From the Cisco edition of November 4, 2026
Cisco says Cisco IQ now exposes production REST APIs and an MCP server, and that scripted tests cut agent tool calls from 256 to 36
Cisco · Vendor; IT operations and lifecycle intelligence relevant to SLED IT · Global
- Publisher
- Cisco Blogs
- Original publication
- Cisco Blogs, Nov. 4, 2026
- Source retrieved
- 2026-11-05
What happened
Cisco says Cisco IQ, generally available since April 2026 and deployed by over 16,000 customers, now offers production REST APIs and a Model Context Protocol server built from one canonical domain model. Agents connecting over MCP inherit the calling principal's permissions through Cisco Unified Identity, with action-level permissions and validated queries that fail loudly rather than being rewritten. In scripted tests on a 17-scenario benchmark corpus, Cisco reports tool calls fell from 256 to 36 and approval prompts from 181 to 1. Live-agent results are not yet published.
Why it matters
Relevant to state, campus and district IT teams that use Cisco IQ for asset, advisory and contract lifecycle data and want AI assistants to query it without creating a separate permission model.
Evidence and measured results
Vendor-authored engineering blog. The benchmark is Cisco's own scripted test on 17 scenarios with no published method, dataset or independent replication; Cisco says live-agent data is still being measured.
Limitations and uncertainty
Self-reported scripted benchmark; 16,000-customer figure unverified; no SLED examples.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-05; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- IT teams spend time stitching asset, advisory and contract data to answer lifecycle and exposure questions.
- Stakeholders
- IT director
- IT asset manager
- Security officer
- Discovery questions
- Do you use Cisco IQ today?
- Which lifecycle or advisory questions take the most staff time?
- Under what identity would an AI assistant run?
- Value hypothesis
- Governed agent access could speed routine lifecycle answers; only vendor scripted data exists.
- Potential engagement
- A read-only Cisco IQ MCP pilot with a local question set.
- Unsupported claims
- Customer productivity gains
- Live-agent performance
- Independent benchmark replication
Pre-sales engineering
Role takeaway
- Fit
- Fits Cisco IQ customers wanting agent access under existing RBAC.
- Architecture and integration
- REST and MCP surfaces from one canonical model; Cisco Unified Identity authorization.
- Prerequisites
- Cisco IQ subscription
- Cisco Unified Identity
- Agent platform with MCP support
- Constraints
- Benchmark is vendor scripted
- Write operations need careful scoping
- Security
- Agents inherit principal permissions; use dedicated least-privilege principals and log calls.
- Proof of value
- Run local question set and record call counts
- Verify role boundary enforcement
- Compare answers to manual reports
Delivery
Role takeaway
- Work
- Read-only agent pilot over Cisco IQ data.
- Dependencies
- Entitlement confirmation
- Identity setup
- MCP-capable agent
- Ownership
- IT asset manager with security review
- Skills and adoption
- Staff need to learn to validate agent answers.
- Governance checkpoints
- Principal and scope approval
- Query logging review
- Write-scope approval gate
- Acceptance criteria
- Proposed: agent answers match manual reports on test set
- Proposed: no access beyond assigned role in tests
- Risks
- Over-trust in vendor benchmark
- Excessive permissions
- Inaccurate answers
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Agents query lifecycle, advisory and contract data through MCP using the same domain model and RBAC as REST clients.
Governance
Who approves, reviews and stays accountable for outcomes?
Agent access inherits existing human role permissions, so role design and least-privilege review become the main control point.
Security and privacy
What data, permissions and controls need testing?
Agents receive only what the calling principal can see; agencies must still check which principal agents run under and log their queries.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
May let smaller teams answer lifecycle and advisory questions faster; no workforce evidence.
Procurement
What should contracts, pricing and exit terms secure?
Check whether API and MCP access is included in existing Cisco IQ entitlements and how partner managed services use the data.
Operating model
Which teams own the service once it runs?
Encourages treating AI assistants as API clients under existing identity governance rather than special integrations.
Publication history
- 2026-11-04Cisco · Issue 073 resources
Stable resource ID: cisco-iq-rest-apis-mcp-server-agent-benchmark-20261104